| Collecting Object References - part 2 [message #118425] |
Sat, 17 November 2007 19:26  |
Eclipse User |
|
|
|
Originally posted by: NOBODY.NOSPAM.COM
Hello,
From what I found in the NG, the latest version of TPTP does not support
collecting object references. The quoted reason was that there is not much
value in this feature.
How so? If a leaked object is referenced by a multitude of other objects
through its life cycle, how can one find the offender that prevents the
leaked object from being GC'ed?
If TPTP supports finding memory leaks through some other (unknown to me)
means, please let me know. At this momemnt, we have a very large Eclipse
RCP-based app, and I cannot find a tool that would help us find memory
leaks.
Regards.
Alex Molochnikov
Kelman Technologies Inc.
|
|
|
| Re: Collecting Object References - part 2 [message #118467 is a reply to message #118425] |
Tue, 20 November 2007 01:30  |
| Eclipse User |
|
|
|
Alex,
> From what I found in the NG, the latest version of TPTP does not support
> collecting object references. The quoted reason was that there is not much
> value in this feature.
I would really like to see this quote :) This feature is important, but
due to resource constraints it is currently deferred for a later
version. There is an enhancement request for this feature in Bugzilla
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=93704). Feel free to add
yourself to the CC list, update comments or vote for this feature.
Regards,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
|
|
|
Powered by
FUDForum. Page generated in 0.06073 seconds
Home