| Tracking resource allocation with Eclipse 3.0 [message #260783] |
Mon, 12 July 2004 11:58  |
Eclipse User |
|
|
|
I have a feeling that my RCP app is leaking resources, and I'd like to do
some diagnostics to try and pin down where from. I understand that Sleak
should help me in doing this. However I'm having great difficulty getting
Sleak to provide me info using Eclipse 3.0. I can see the Sleak view, but
pressing the buttons report "Warning: Device is not tracking resource
allocation".
Prompted by replies to previous newsgroup messages, I have tried the
following:
1) Set Device.DEBUG to true prior to the display being created.
2) Included org.eclipse.swt and org.eclipse.swt.win32 in my workspace.
3) Set tracing on org.eclipse.ui.
None of these work and the same report is given from the Sleak view.
Does anyone have any suggestions of a) how I can get Sleak working; or b)
an alternative method for tracing resource allocation and deallocation
within the context of an Eclipse 3.0 RCP app.
Many thanks.
James
|
|
|
| Re: Tracking resource allocation with Eclipse 3.0 [message #261469 is a reply to message #260783] |
Wed, 14 July 2004 10:27  |
| Eclipse User |
|
|
|
James,
I'm surprised that suggestion #1 didn't work for you, as I tried with a
small snippet (though not an RCP app) and it set the behaviour properly.
Try the following when creating your display, as an alternative means of
setting the tracking variable:
DeviceData data = new DeviceData ();
data.tracking = true;
data.debug = true;
Display display = new Dipslay (data);
Grant
"James Willans" <jwillans@cs.york.ac.uk> wrote in message
news:ccucec$l3k$1@eclipse.org...
> I have a feeling that my RCP app is leaking resources, and I'd like to do
> some diagnostics to try and pin down where from. I understand that Sleak
> should help me in doing this. However I'm having great difficulty getting
> Sleak to provide me info using Eclipse 3.0. I can see the Sleak view, but
> pressing the buttons report "Warning: Device is not tracking resource
> allocation".
>
> Prompted by replies to previous newsgroup messages, I have tried the
> following:
>
> 1) Set Device.DEBUG to true prior to the display being created.
>
> 2) Included org.eclipse.swt and org.eclipse.swt.win32 in my workspace.
>
> 3) Set tracing on org.eclipse.ui.
>
> None of these work and the same report is given from the Sleak view.
>
> Does anyone have any suggestions of a) how I can get Sleak working; or b)
> an alternative method for tracing resource allocation and deallocation
> within the context of an Eclipse 3.0 RCP app.
>
> Many thanks.
>
> James
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03002 seconds
Home