Bug 294043 - Investigate ways to test temporary memory consumption
Summary: Investigate ways to test temporary memory consumption
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2009-11-03 06:17 EST by Pawel Pogorzelski CLA
Modified: 2019-09-06 16:14 EDT (History)
4 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 Pawel Pogorzelski CLA 2009-11-03 06:17:30 EST 
Some resources operations cause transient heap consumption that can lead to OutOfMemoryError. These are for example workspace refresh and crash recovery. See bug 245008 and bug 292267 for details.

Right now there isn't a way to reliably measure this temporary memory utilization. This bug is to investigate whether introducing such tests is feasible.
Comment 1 Pawel Pogorzelski CLA 2009-11-03 06:33:32 EST 
Martin and Boris had some interesting discussion about that on the mailing list. For details go to http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg01395.html.
Comment 2 Szymon Brandys CLA 2010-04-12 06:40:32 EDT 
No plans to do it for 3.6.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:14:40 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.