This question is locked. New answers and comments are not allowed.
Hi,
The subject pretty much says it all. I'm trying to hunt down known leaks on a C# Windows store app, and I've found the leaked objects easily (JT correctly identifies them as likely leaks). However, when I try to find out whats holding a reference to them with the "Show paths to GC roots" command, all I get is the object itself in blue (GC root - cannot be collected.) It doesn't make much sense for these objects to be GC roots, and I know that the GC-path function is working because for other objects I get an actual reference hierarchy.
Thanks for the help!
mike
The subject pretty much says it all. I'm trying to hunt down known leaks on a C# Windows store app, and I've found the leaked objects easily (JT correctly identifies them as likely leaks). However, when I try to find out whats holding a reference to them with the "Show paths to GC roots" command, all I get is the object itself in blue (GC root - cannot be collected.) It doesn't make much sense for these objects to be GC roots, and I know that the GC-path function is working because for other objects I get an actual reference hierarchy.
Thanks for the help!
mike
1 Answer, 1 is accepted
0
Hi Mikhail,
Thank you for contacting us.
In most of the cases, such roots are being held by the unmanaged parts of your application. And JustTrace is not able to show them as at this stage it profiles only managed code.
However, to be sure there isn't a bug on our side, I would suggest you to isolate this in a simple repro project and send it over for investigation.
Regards,
Kaloyan
Telerik
Thank you for contacting us.
In most of the cases, such roots are being held by the unmanaged parts of your application. And JustTrace is not able to show them as at this stage it profiles only managed code.
However, to be sure there isn't a bug on our side, I would suggest you to isolate this in a simple repro project and send it over for investigation.
Regards,
Kaloyan
Telerik