Bug 2341 - [JFace] Out of memory errors reported as null (1GET7EQ)
Summary: [JFace] Out of memory errors reported as null (1GET7EQ)
Status: RESOLVED DUPLICATE of bug 2051
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Linux
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:34 EDT by Tod Creasey CLA
Modified: 2001-12-19 16:16 EST (History)
0 users

See Also:

Attachments
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 Tod Creasey CLA 2001-10-10 22:34:27 EDT 
If you get an OutOfMemoryError from Java when rebuilding the world the error message is
"Errors Building: null". On the console you will get an error exception in GlobalBuildAction.run()
java.lang.OutOfMemory error. The user should be informed it was an out of memory error


NOTES:
EG (6/4/2001 11:47:03 AM)
	The GlobalBuildAction is contributed by ITPUI and not JDT. There isn't a lot
	of data in this PR. In general ISVs should not catch runtime exceptions but let them
	propagate to the platform where they are handled. Moving to ITPUI.

JM (6/5/2001 10:43:58 PM)
	I suspect this is NOT one of the null message problems we were seeing with Status objects
	unless someone's IStatus implementation is being more premissive and generating a string.
	The standard Status will assert that the message is not null
Comment 1 DJ Houghton CLA 2001-10-29 18:21:22 EST 
PRODUCT VERSION: 118
Comment 2 Kevin Haaland CLA 2001-12-19 16:16:06 EST 

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