GNOME Bugzilla – Bug 405368
Java process does not exit when Accessibility is enabled
Last modified: 2007-03-19 05:48:26 UTC
Please describe the problem: Using Ubuntu Edgy with kernel 2.6.17.14, Eclipse IDE 3.2.1, Sun Java JRE 1.5.0_08-b03. When Eclipse is closed it's process remains in memory and requires "kill -KILL pid". If Assistive Technologies are disabled in System > Preferences the Java application closes cleanly. Steps to reproduce: 1. Enable Assistive Technologies 2. Start Eclipse 3. Close Eclipse 4. "ps -efly | grep eclipse" to show process remains running. Repeat with Assistive Technologies disabled. Actual results: The process remains in memory. Expected results: The process to clean up and exit. Does this happen every time? Yes. Other information: There's an Ubuntu bug covering this issue, although most reporters don't appear to have cross-referenced it here: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/68714
Could this be eclipse-specific? I've never encountered reports of this happening with other Java apps using the Sun JRE.
Hmmm,that is possible. We need another large Java application that makes use of the bridge in the same way, I guess. Any ideas of what else to test? This Assistive Technologies field is your baby - I only got here because of the affects on my Eclipse environment :)
reassign to Jeff Cai.
In fact, eclipse is a gtk-based application. After you start eclipse, you can see $./eclipse GTK Accessibility Module initialized. This means gtk bridge has been loaded but not java bridge. If you close eclipse, eclipse can exit successfully except you have to wait for a little longer time, about 10-20 seconds.
BTW, I tested it on Ubuntu Feisty. and eclipse's version is EasyEclipse Expert Java 1.2.1 The stack trace I get makes no sense: (gdb) bt
+ Trace 118776
I don't know whether eclipse has a version for Solaris because my development environment is on Solaris. Or, can you get a meaningful stack trace for me when eclipse is waiting for something?