Scenarios for finding leaks in M6

The following are the scenarios that have been checked for leaks. The method used to check for leaks was to execute the scenario in question, then manually look for leaking objects with a heap analysis tool.

Views

checked all views contributed by ZRH. The scenario was:

• Open View
• Close View
• Check that the view (and associated objects) have gone away.

The following views have been checked: Package Navigator, Type Hierarchy, Projects, Packages, Types, Members, Call Hierarchy, Declaration, Javadoc, Search.

Perspectives

The three perspectives Java, Java Browsing and Type Hierarchy have been checked with the following Scenario

• Open the perspective
• Close the perspective
• Check that the perspective object has gone away.

Smoke Test

Followed the JDT Smoke Test up to (but not including) the editing section, inspecting the heap after each step. Additionally, the following sections where checked for leaks:

• Type Hierarchy Secion

• Compare Section
• Local History

Editors

Opened and closed CompilationUnitEditor, ClassFileEditor and TextEditor and check that the editor instances went away.

Refactoring

Checked the following refactorings: Rename, Move, Inline, Extract method, Generalize Type. Checked that no TextChanges stick around and that the preview editor goes away.

Other

We also ran Eclipse in normal development for a day and inspected a heap dump afterwards.