Community
Participate
Working Groups
Build Identifier: 20110615-0604 (Indigo) I upgraded from Helios to Indigo last Friday. Eclipse freezes to death. There's no error message, just unresponsive IDE. - I have no trace of it in Eclipse error log (Eclipse freezes and that's it, cursor shows it's busy, system tells it's non-responsive and it will sit there like that till I kill it - tried hours with no effect) - it's not a performance problem (it uses 580MB and I set heap to use 1GB, CPU used is less than 10% - upon killing, I always have info that exit code returned is -805306369 New workspace helps, so I gave this a minor bug priority. Still - don't know why I had to change workspaces - old one worked well for nearly a year. My memory settings: 512 (max) perm size; 1024 Xm(s)x. I can open About dialog, I can browse menu (but not a nested one! entering menu from rendered menu just freezes Eclipse!) and I can revert (some) configs, but revert to Helios can't happen due to error in repository. Also, running Eclipse as admin with -clean didn't work. Any ideas? Reproducible: Always Steps to Reproduce: 1. Open menu (e.g. File, or Run) and then open a submenu there OR 2. Try switch perspective to Debug (via keys or mouse or menu) OR 3. Work for a while
Get a thread dump when Eclipse has hung. http://wiki.eclipse.org/index.php/How_to_report_a_deadlock
Move to Platform/Runtime
Apologies for belated answer. Remy, unfortunately I won't have the thread dump. Not unless the issue repeats itself. I dumped that workspace and started off with a new one. Not all imports worked due to workspace crashing when submenu* was to be rendered, but I managed some and recreated what I remembered. Feel free to close this, unless someone else has the same issue and wishes to keep this going. I can't replicate this anymore so from my side - clearance to close. * for clarity: like File > New or Window > Navigation. In both cases New and Navigation are submenus.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Closing out old bug that is not reproducible at this time.
