Finding SWT Resource Leaks with Sleak
Not all elements are automatically released in SWT. You need to call dispose() on Color, Cursor, Display, Font, GC, Image, Printer, Region and Widget. In order to ensure we're not leaking these resources, we've integrated a customized version of Sleak for our examples.
Gradle automatically creates a corresponding Sleak task for each example. To start it up, simply run
./gradlew runExample<ExampleName>Sleak
For instance, running
./gradlew runExampleBubbleSleak
will pull up a blank Sleak window.
At this point, run an initial Capture by pressing the Capture button. This will give you an idea of the baseline resources used by the Sleak window (and the OS).
Next, click Run Example and run another Capture. This will show you what additional resources you're using while the example is running.
You might want to run a few additional captures to make sure that you're not leaking resources while the example is running (e.g. you might be creating a GC on each PaintEvent and not disposing it). Next, close the Shell running the example. This will tell your widget(s) that it needs to handle the dispose.
Run another capture. You should see the resources drop back to the initially allocated amounts (what you saw on your first capture).
If you see more elements than you originally saw, your widget is not properly managing its resources. Investigate the problem and stop the leak!