Bug 241773 - Could not exit workbench due to some internal error
Summary: Could not exit workbench due to some internal error
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-23 00:54 EDT by David Williams CLA
Modified: 2009-05-04 11:27 EDT (History)
6 users (show)

See Also:


Attachments
log from session (59.49 KB, text/plain)
2008-07-23 00:54 EDT, David Williams CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2008-07-23 00:54:36 EDT
Created attachment 108162 [details]
log from session

I'm not sure what the "root" error is here (see attached log) but it prevented the workspace from exiting, and I had to kill the process. 

Seems the workbench should always be able to exit in some fashion, so thought I'd open this bug here if you were interested in these traces. 

If it's an isolated case, I wouldn't spend too much time on it ... but, if you get a number of such reports, you'll at least have more stack traces to compare. 

Thanks,
Comment 1 Simos Xenitellis CLA 2008-08-05 14:42:55 EDT
I have a similar situation with Eclipse 3.4 on Linux 64bit, where the Eclipse process (java) would get stuck when you exit, and require a process termination.
Comment 2 Simos Xenitellis CLA 2008-08-15 06:24:10 EDT
I managed to figure out that in my case (in Linux), the problem was related to the fact that the accessibility features (ATK) where enabled in my session.
Once I disabled the accessibility features, Eclipse could exit cleanly.

See http://bugzilla.gnome.org/show_bug.cgi?id=546542
Comment 3 Thomas Watson CLA 2008-08-15 09:18:26 EDT
David, did this happen more than once?  After you killed the process and restarted did it happen again?  I am curious if you deleted the D:\builds\JEEIDE\eclipse\configuration\org.eclipse.osgi\ directory while eclipse was up and running.  Perhaps you ran another eclipse session with -clean against that configuration at the same time?
Comment 4 David Williams CLA 2008-08-15 10:13:20 EDT
No, mine did not happen more than once. Fairly sure I didn't delete D:\builds\JEEIDE\eclipse\configuration\org.eclipse.osgi\ or run again with -clean ... but, could have. Sounds like this -clean issue would be a repeatable problem? 



Comment 5 Ilan CLA 2008-09-18 08:31:35 EDT
Related bug report: 247705

I files the above report yesterday.
It is definitely related to this bug report, except that in my case the problem repeats itself. I am going to attempt the Simos Xenitellis workaround by turning off the accessibility feature (in the next 15 minutes).

I will add an additional comment to this bug report if the workaround succeeds.
Comment 6 Ilan CLA 2008-09-18 09:01:07 EDT
My workaround attempt:
1. Open the "System>Preferences>Assistive_Technologies" control panel.
2. Switch off the "Enable Assistive Technologies" value.
3. Invoke Eclipse.
4. Select "File>Exit" in Eclipse.
5. Did a "ps -ef | grep eclipse".
6. Noticed that the process was still running.
7. Rebooted the system.
8. Repeated steps 3-5, above.
9. The problem was eliminated.
10. Attempted to make Eclipse fail again, several times. I Could NOT!

A way to repeat the problem, for debugging purposes:
1. Switch on the Assistive Technologies capability.
2. Reboot.
3. Run Eclipse and then exist Eclipse.
4. Verify that the Eclipse process is still running, using "ps -ef".
Comment 7 Ilan CLA 2008-09-18 09:06:51 EDT
*** Bug 247705 has been marked as a duplicate of this bug. ***
Comment 8 Simos Xenitellis CLA 2008-09-18 09:17:02 EDT
Thanks Ilan for replicating.

A few things to note:

1. This bug report mentioned WindowsXP in the OS field. This should be changed to Linux. I do not think that the same problem exists in WXP. David?

It is possible that we are mixing two different bugs in this report (if WXP fails, but unrelated to Assistive Technologies).

2. When you change the settings in Assistive Technologies in Linux, you need to logout and re-login again, so that the new settings are activated. It is not required to reboot.

3. The subject of this report (Assistive Technologies + Linux) should be changed to something like (Assistive Technologies in Linux make Eclipse to fail exit).
Comment 9 Remy Suen CLA 2008-12-31 08:48:56 EST
(In reply to comment #8)
> 1. This bug report mentioned WindowsXP in the OS field. This should be changed
> to Linux. I do not think that the same problem exists in WXP. David?
> 
> It is possible that we are mixing two different bugs in this report (if WXP
> fails, but unrelated to Assistive Technologies).

From David's log in attachment 108162 [details], it is clear that he is on Windows so I think we should create another bug report.
Comment 10 Remy Suen CLA 2009-01-04 17:22:02 EST
*** Bug 259920 has been marked as a duplicate of this bug. ***
Comment 11 John Arthorne CLA 2009-05-02 11:55:35 EDT
*** Bug 274718 has been marked as a duplicate of this bug. ***
Comment 12 Thomas Watson CLA 2009-05-04 11:27:27 EDT
I moved the ubuntu related bugs with "Assistive Technologies" to bug 247705.  This bug is being left to the strange errors David was getting on Windows.

I am closing this bug as works for me.  David if you can reproduce this again, please reopen.