Bug 156486 - [ErrorHandling] Eclipse failed to load after OoM
Summary: [ErrorHandling] Eclipse failed to load after OoM
Status: RESOLVED DUPLICATE of bug 72463
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Kim Horne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-07 03:37 EDT by Sergey Vladimirov CLA
Modified: 2007-02-01 15:53 EST (History)
2 users (show)

See Also:


Attachments
Example XML file to load with WST (229.58 KB, application/x-zip-compressed)
2006-09-07 03:38 EDT, Sergey Vladimirov CLA
no flags Details
Part of log (5.20 KB, text/plain)
2006-09-08 04:58 EDT, Sergey Vladimirov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Vladimirov CLA 2006-09-07 03:37:29 EDT
After opening big XML file (in attach) Eclipse exits with OoM exception and not starts again (trying to reopen the same file?)

Workaround... to modify workspace\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml and remove editor link.
Comment 1 Sergey Vladimirov CLA 2006-09-07 03:38:11 EDT
Created attachment 49584 [details]
Example XML file to load with WST
Comment 2 David Williams CLA 2006-09-07 12:41:47 EDT
ooo, that's nasty ... an infinit loop crash! 

Sergy, can you attach any .log files generated? I want to see if workbench is detecting that is recoverying from a crash ... if so, I'll move this to platform, as I suspect in those cases it should never try to re-open editors. 





Comment 3 Sergey Vladimirov CLA 2006-09-08 04:58:48 EDT
Created attachment 49695 [details]
Part of log

Not sure, if it's required part of log.

David, i think you can try to open attached example in WST and see it by yourself (if you aren't scared of non-starting Eclipse ;) )
Comment 4 David Williams CLA 2006-12-20 00:45:44 EST
Moving to platform UI for consideration. 

I could reproduce this problem, by using a low max heap (e.g. 100M) but the principle is the same, no matter what the heap size (and no matter how efficient our editor will become :) 

Seems to me that if the workbench starts, it currently recognizes that it did not shutdown cleanly (shut down from out of memory error) and then when it restarts it _should_ start up in some sort of clean state ... such as to not try and open editors that were open when it shut down. Or ... at least give the user a choice. I've noticed that's what modern tabbed browsers such as firefox and opera do ... that is when they recognize they did not end gracefully, they ask the user if they want to restore sessions, or start with fresh session. 



Comment 5 Kim Horne CLA 2007-02-01 15:53:10 EST

*** This bug has been marked as a duplicate of bug 72463 ***