Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 79985 - [ErrorHandling] Add improved tools to track down out of memory errors
Summary: [ErrorHandling] Add improved tools to track down out of memory errors
Status: RESOLVED DUPLICATE of bug 33972
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Szymon Brandys CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-02 06:00 EST by Oyvind Harboe CLA
Modified: 2007-06-22 14:59 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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 ***