Bug 2051 - Out of memory should be shown to the user (1GDUXCD)
Summary: Out of memory should be shown to the user (1GDUXCD)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P2 major (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Eduardo Pereira CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 2341 2404 2610 2611 2758 7006 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 22:25 EDT by Dani Megert CLA
Modified: 2002-01-31 18:18 EST (History)
6 users (show)

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 Dani Megert CLA 2001-10-10 22:25:25 EDT 
After a (long) time of working with Eclipse I had an Out Of Memory
	Exception. Eclipse disappeared without showing an error dialog/warning.
	I only noticed it because I had a "pause" in my batch file.

	(Did not check the log - guess it may be in there but this is not enough)


NOTES:
Comment 1 DJ Houghton CLA 2001-10-29 17:48:15 EST 
PRODUCT VERSION:
	SDK 0.107, CVS, Self Hosting
Comment 2 Kevin Haaland CLA 2001-12-19 16:16:07 EST 
*** Bug 2341 has been marked as a duplicate of this bug. ***
Comment 3 Kevin Haaland CLA 2001-12-19 16:16:23 EST 
*** Bug 2611 has been marked as a duplicate of this bug. ***
Comment 4 Kevin Haaland CLA 2001-12-19 16:16:38 EST 
*** Bug 2758 has been marked as a duplicate of this bug. ***
Comment 5 Kevin Haaland CLA 2001-12-19 16:16:52 EST 
*** Bug 7006 has been marked as a duplicate of this bug. ***
Comment 6 Nick Edgar CLA 2002-01-18 12:19:29 EST 
*** Bug 2404 has been marked as a duplicate of this bug. ***
Comment 7 Nick Edgar CLA 2002-01-18 12:20:36 EST 
*** Bug 2610 has been marked as a duplicate of this bug. ***
Comment 8 Nick Edgar CLA 2002-01-18 12:22:01 EST 
See stack dump in bug 7006.
Comment 9 Nick Edgar CLA 2002-01-18 12:25:36 EST 
Should fix for M3.

Should write a test plugin which allocates memory (e.g. 10M chunks) until it 
dies.
The Workbench should recover gracefully if it can.
Note that in this example, the last 10M allocation will have failed, but there 
should be enough memory free to warn the user, then shut down gracefully if 
that's what they want.

As another example, a plugin should be able to try allocating 1G of memory and 
not crash Eclipse.  It should run just as well after as before the attempt.
Comment 10 Nick Edgar CLA 2002-01-18 12:26:27 EST 
See also bug 6825.
Comment 11 Eduardo Pereira CLA 2002-01-31 17:23:39 EST 
A fix has being released. It will still fail to report the problem to the user 
depending on how the "Out of memory error" hapenned. If it failed allocating a 
lot of bytes then we have a good change to report the problem to the user but 
if it failed allocanting one single object the it is likely that we do not have 
memory to report the problem.

The current fix is opening a dialog warning the user and asking if he wants to 
exit the workbench. This warning/logging/exiting is all wrapped with try{}catch 
blocks.
Comment 12 Knut Radloff CLA 2002-01-31 18:18:54 EST 
Can we allocate a dummy object on startup that takes up enough memory to 
guarantee a message dialog and proper shutdown (e.g., 500k) and that is 
dereferenced immediately when an OutOfMemoryException occurs?