Bug 7006 - Eclipse dies silently when running out of memory
Summary: Eclipse dies silently when running out of memory
Status: RESOLVED DUPLICATE of bug 2051
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-17 12:31 EST by Knut Radloff CLA
Modified: 2001-12-19 16:16 EST (History)
0 users

See Also:

Attachments
OutOfMemoryError in Synchronizer.runAsyncMessages (1.40 KB, text/plain)
2001-12-17 12:32 EST, Knut Radloff CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Radloff CLA 2001-12-17 12:31:14 EST 
build 20011206

I have a fairly average sized workspace (org.eclipse.swt, 
org.eclipse.swt.tests, org.eclipse.swt.internal), running on J9.
After using Eclipse for about an hour (debugging, compiling) the memory load 
was at 170MB.
At some point the UI got really unresponsive (i.e., slow text editing, slow 
code assist). I looked in the .log and there was an OutOfMemoryError in SWT. I 
never got an internal error message box. I continued for a little while before 
Eclipse silently crashed. No GPF, no .log entry, it just disappeared.
Considering that Eclipse seems very likely to exceed the default heap size an 
out of memory error should be displayed to the user and appropriate action 
suggested (exit immediately, increase VM heap size).
Comment 1 Knut Radloff CLA 2001-12-17 12:32:03 EST 
Created attachment 187 [details]
OutOfMemoryError in Synchronizer.runAsyncMessages
Comment 2 John Arthorne CLA 2001-12-17 14:10:37 EST 
The workbench event loop and error handling is in the UI.  Moving to UI for 
consideration.
Comment 3 Kevin Haaland CLA 2001-12-19 16:16:51 EST 

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