Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353772 - [Forms] disposed ComplexImageDescriptor images are keep in memory
Summary: [Forms] disposed ComplexImageDescriptor images are keep in memory
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 10:19 EDT by Flavio Donze CLA
Modified: 2019-11-14 03:40 EST (History)
3 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 Flavio Donze CLA 2011-08-03 10:19:38 EDT 
Build Identifier: 3.6.1

FormImages.markFinished() does not remove the image and it's ComplexImageDescriptor from the local HashMap "descriptors".

descriptors.remove(image); is called but the image remains in the map, probably because it is disposed earlier in (resourceManager.destroyImage(desc);).

Tested this behavior with the mail example, adding org.eclipse.ui.forms to it's dependencies and the following code in the view:

FormToolkit toolkit = new FormToolkit(Display.getCurrent());
Form form = toolkit.createForm(parent);
toolkit.decorateFormHeading(form);


using: org.eclipse.ui.forms 3.5.2



Reproducible: Always
Comment 1 Paul Webster CLA 2011-08-03 10:32:29 EDT 
Chris, are we still managing Forms and Browser under UA, now that they're in the platform ui ACL (I don't remember what the final word was)?

PW
Comment 2 Chris Goldthorpe CLA 2011-08-15 13:17:13 EDT 
Yes, UI forms bugs still fall under User Assistance. We may want to revisit that at some time in the future but for now they fall under UA.
Comment 3 Lars Vogel CLA 2019-11-14 03:40:05 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.