Sleak in RCP: Device is not tracking resource allocation

Question

I have tried to make Sleak work on my Indigo RCP application. I have followed the steps on this guide. I.e. I have installed the plugin, added the swt tools plugin to curren

Answer 1

I faced the same problem recently, and managed to find a solution. Here's what I found, who knows it might help you.

On RCP startup, there's a call to PlatformUI.createDisplay(), which chains to a call to Workbench.createDisplay(). That's the exact point where the debug settings needed by Sleak are properly read and set.

What happened on our software was that a call to Display.getDefault() was made BEFORE the above call to PlatformUI.createDisplay(). It caused the creation of a new Display object, which was set as the default. This creation did not read and set the debug settings.

By the time our code got to the PlatformUI.createDisplay() call, it didn't actually create a new Display. Instead, it returned the previously-created, not-debug-friendly one. Thus leading Sleak into warning about "device not tracking resource allocation".

Adding a breakpoint at the method Display.register (Display display) helped us identifying the early creation origin and properly change it.

Answer 2

I think you haven't set these properties correctly:

org.eclipse.ui/debug=true
org.eclipse.ui/trace/graphics=true