Bug 222723

Summary:	EditionHistoryPage consumes more than 60 Mo of memory in my workspace
Product:	[Eclipse Project] Platform	Reporter:	Frederic Fusier <frederic_fusier>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Frederic Fusier

2008-03-14 06:29:12 EDT

Build I20080305-1100.

I'm working in an eclipse session started with default memory parameters value (e.g. -Xmx256M -Xms40M). Since a while, the consumed memory was near the Java Heap size and I needed to analyze the memory snapshot using yourkit before an OOME occurred

The object consuming the biggest amount of memory was the EditionHistoryPage and more specifically the Map 'editions' which was over 60 Mo. Note that forced garbage collections didn't change anything...

Seeing this, I tried to close all the History view in my session. I had 5 opened windows and 4 of them had an History view opened and populated but none of them were on top of the tabs (e.g. not selected) . After having closed all these History views, I forced again a garbage collection and then the memory was released :-).

Then, I finally reopened the History view in the 4 windows, see that more than 60 Mo of memory was consumed again, but this time, the garbage collection released the memory!

So, it seems that before closing all the History views I fell in a state where the 'options' Map of EditionHistoryPage was always referenced and couldn't be garbaged (might be a VM issue while garbaging...!?).

I open this bug just to warn about a potential issue in this area and let you verify if this can happen in certain circumstances... Feel free to close if your verification shows that it can never happen.

Comment 1 Eclipse Webmaster

2019-09-06 16:06:02 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.