| commit | 81e764b3b98e971702e955b15c6ac7f3997e071b | [log] [tgz] |
|---|---|---|
| author | Remy Suen <remysuen@ca.ibm.com> | Fri Feb 10 15:10:59 2012 -0500 |
| committer | Remy Suen <remysuen@ca.ibm.com> | Fri Feb 10 15:10:59 2012 -0500 |
| tree | ec304e5c98452f695bf6809b3916f91ef23ba176 | |
| parent | fc249c2be4fb75fb2cc37fb70546c288642a234f [diff] |
Bug 348069 Closing an additional window of an Eclipse 4 application doesn't unrender it When a window was being closed, only its widgets were destroyed and its context structure was not. This leads to memory leaks. If a top-level window gets closed, its entire structure and context will be destroyed and the window itself will be removed from the application's list of child windows if it is not the last window in the list. If it is the last window, then the window's structure and contexts will be destroyed but it will not be removed from the application's list of child windows for restart purposes. For detached windows, detached windows will have always have their structures and contexts destroyed but it will only remove itself from its parent list of child windows if the detached window being destroyed does not contain any parts.
Platform UI provides the basic building blocks for user interfaces built with Eclipse. Some of these form the Eclipse Rich Client Platform (RCP) and can be used for arbitrary rich client applications, while others are specific to the Eclipse IDE. The Platform UI codebase is built on top of the Eclipse Standard Widget Toolkit (SWT), which is developed as an independent project.
For more information, refer to the [Platform UI wiki page] 1.