Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357063 - [MinMax] Leak when maximize + restore again a view
Summary: [MinMax] Leak when maximize + restore again a view
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 07:44 EDT by Martin Spurek CLA
Modified: 2019-09-02 13:05 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Spurek CLA 2011-09-08 07:44:07 EDT
Build Identifier: 3.5.0

I used a "sleak" utility to find out that the handle is region allocated in org.eclipse.ui.internal.LegacyAnimationFeedback (line 71), however did not recognize where the leak really happens.
It can be easily observed also without the sleak, simple using windows task manager, keep the UI to stabilize the handles. Then always when you maximize and restore the view the coutn of GDI objects is always bigger by 1.

Reproducible: Always

Steps to Reproduce:
1. open some eclipse ui with bunch of views
2. check GDI objects count
3. maximize the view (either double click on title or button)
4. restore the view to original perspective state (either double click on title or button)
5. check GDI objects count

Always you repeat 3. - 5. the count is 1 handle higher.
Comment 1 Eclipse Genie CLA 2019-09-02 13:05:10 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.

--
The automated Eclipse Genie.