Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 188351 - [StatusHandling] Multiple dialogs after OutOfMemoryError
Summary: [StatusHandling] Multiple dialogs after OutOfMemoryError
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.5   Edit
Assignee: Krzysztof Daniel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-22 11:49 EDT by Szymon Brandys CLA
Modified: 2009-03-17 10:27 EDT (History)
0 users

See Also:

Attachments
Illustrates the problem (5.39 KB, application/octet-stream)
2007-05-23 04:21 EDT, Szymon Brandys CLA 		no flags Details
Screenshot (36.68 KB, image/png)
2009-03-03 12:01 EST, Krzysztof Daniel 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 Szymon Brandys CLA 2007-05-22 11:49:22 EDT 
It is a bug for the case Tod observed during fixing Bug173049

Tod wrote:

However here is an example that generates 10 OutOfMemory exceptions and still opens several dialogs. Given how late in the game this is I think we should look at this case for 3.3.1 or 3.4.

STEPS
1) Load a plug-in into your workspace
2) Select your manifest file
3) Popup New Submeny - > Out of Memory Test
Comment 1 Szymon Brandys CLA 2007-05-23 04:21:03 EDT 
Created attachment 68293 [details]
Illustrates the problem
Comment 2 Szymon Brandys CLA 2008-06-09 10:57:59 EDT 
To address in 3.5.
Comment 3 Krzysztof Daniel CLA 2009-03-03 12:01:23 EST 
Created attachment 127341 [details]
Screenshot

The issue must have been fixed by introducing synchronization while creating the status manager.

I'll close this as WORKSFORME before the end of the week if you do not mind.
Comment 4 Krzysztof Daniel CLA 2009-03-17 10:27:50 EDT 
After deeper investigation:

The issue occurs when there is no thread left for handling jobs. All threads are waiting (because OOME is blocking). After the dialog is closed, remaining jobs are run and further errors are reported.

Observed behavior is a limitation of choosen architecture.