Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 79985

Summary: [ErrorHandling] Add improved tools to track down out of memory errors
Product: [Eclipse Project] Platform Reporter: Oyvind Harboe <oyvind.harboe>
Component: UIAssignee: Szymon Brandys <Szymon.Brandys>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3    
Version: 3.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Oyvind Harboe CLA 2004-12-02 06:00:02 EST 
I've got 1Gbyte of working space, but I get the error below during normal
operations from time to another.

Would it be possible to add some mechanism to put a bit more flesh on these
problem conditions such that they be tracked down more easily?


The latest case was when double clicking on a text file in the search view of
Eclipse 3.0.1.


Unhandled event loop exception
Reason:
Failed to execute runnable (java.lang.OutOfMemoryError)
*** SWT nested exception
Reason:
java.lang.OutOfMemoryError
Unhandled event loop exception
Comment 1 Szymon Brandys CLA 2007-06-22 14:59:49 EDT 

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