| finding a memory leak [message #24108] |
Mon, 01 August 2005 14:19  |
Eclipse User |
|
|
|
Hi,
I am using TPTP 4.0.0 to try and find a memory leak which shows up after
a long time of running tests.
I can see one class of object that has more than the number of expected
instances, but I can't find out how to get the stack trace of where
these instances are allocated (or at least which objects point to these
instances).
I looked at the documentation that is around and see that enabling
instance level object collection should show at least some of this
information. I have tried to do that, but the number of references and
details columns in the object references view are consistently blank,
and each line of object reference never has subordinate objects.
Is there something I am missing?
Thanks,
Francis
|
|
|
|
| Re: finding a memory leak [message #24335 is a reply to message #24144] |
Tue, 02 August 2005 11:43  |
| Eclipse User |
|
|
|
Hi Francis,
Yes, Object reference information can be collected while your application
under profile is live running, via 'Collect Object Reference' action in
Profile Monitor View action toolbar or under context menu of Process in the
Monitor View. These are the only way to collect object reference
information, and there is no automatic object reference collection support
in TPTP.
After you perform a collect object reference action, please refresh the
Object Reference view to show the most updated information. Please note that
Object Reference view can shown either 'Reference To' or 'Reference By'
orientation, via the drop down button of the view toolbar.
Hope this help.
Eugene
"Francis Upton" <francisu@ieee.org> wrote in message
news:dcn41c$n8m$1@news.eclipse.org...
> I figured out how to get the object references; apparently you have to
> do this while the test is running. Is this the only way to do this?
> Can it be set up to automatically collect the references?
>
> Is there a way to get a stack trace associated with the references (like
> what hat can do?).
>
> Thanks,
>
> Francis
>
> Francis Upton wrote:
> > Hi,
> >
> > I am using TPTP 4.0.0 to try and find a memory leak which shows up after
> > a long time of running tests.
> >
> > I can see one class of object that has more than the number of expected
> > instances, but I can't find out how to get the stack trace of where
> > these instances are allocated (or at least which objects point to these
> > instances).
> >
> > I looked at the documentation that is around and see that enabling
> > instance level object collection should show at least some of this
> > information. I have tried to do that, but the number of references and
> > details columns in the object references view are consistently blank,
> > and each line of object reference never has subordinate objects.
> >
> > Is there something I am missing?
> >
> > Thanks,
> >
> > Francis
|
|
|
| Re: finding a memory leak [message #26211 is a reply to message #24335] |
Thu, 11 August 2005 17:10 |
| Eclipse User |
|
|
|
Originally posted by: dawood.us.ibm.com
So, this seems to imply that you only get a snapshot of the references
sometime around the time you push the button. Is this correct, or does
this button somehow cause reference reporting to continue from that
point on?
Eugene Chan wrote:
> Hi Francis,
>
> Yes, Object reference information can be collected while your application
> under profile is live running, via 'Collect Object Reference' action in
> Profile Monitor View action toolbar or under context menu of Process in the
> Monitor View. These are the only way to collect object reference
> information, and there is no automatic object reference collection support
> in TPTP.
> After you perform a collect object reference action, please refresh the
> Object Reference view to show the most updated information. Please note that
> Object Reference view can shown either 'Reference To' or 'Reference By'
> orientation, via the drop down button of the view toolbar.
>
> Hope this help.
> Eugene
>
> "Francis Upton" <francisu@ieee.org> wrote in message
> news:dcn41c$n8m$1@news.eclipse.org...
>
>>I figured out how to get the object references; apparently you have to
>>do this while the test is running. Is this the only way to do this?
>>Can it be set up to automatically collect the references?
>>
>>Is there a way to get a stack trace associated with the references (like
>> what hat can do?).
>>
>>Thanks,
>>
>>Francis
>>
>>Francis Upton wrote:
>>
>>>Hi,
>>>
>>>I am using TPTP 4.0.0 to try and find a memory leak which shows up after
>>>a long time of running tests.
>>>
>>>I can see one class of object that has more than the number of expected
>>>instances, but I can't find out how to get the stack trace of where
>>>these instances are allocated (or at least which objects point to these
>>>instances).
>>>
>>>I looked at the documentation that is around and see that enabling
>>>instance level object collection should show at least some of this
>>>information. I have tried to do that, but the number of references and
>>>details columns in the object references view are consistently blank,
>>>and each line of object reference never has subordinate objects.
>>>
>>>Is there something I am missing?
>>>
>>>Thanks,
>>>
>>>Francis
>
>
>
|
|
|
| Re: finding a memory leak [message #26333 is a reply to message #26211] |
Fri, 12 August 2005 11:24 |
| Eclipse User |
|
|
|
Hi.
Yes. It is a snapshot of the object reference at the moment you ask to
collect the information. It does not do continuous collection of object
reference information.
"David Wood" <dawood@us.ibm.com> wrote in message
news:ddget2$ga8$1@news.eclipse.org...
> So, this seems to imply that you only get a snapshot of the references
> sometime around the time you push the button. Is this correct, or does
> this button somehow cause reference reporting to continue from that
> point on?
>
>
> Eugene Chan wrote:
> > Hi Francis,
> >
> > Yes, Object reference information can be collected while your
application
> > under profile is live running, via 'Collect Object Reference' action in
> > Profile Monitor View action toolbar or under context menu of Process in
the
> > Monitor View. These are the only way to collect object reference
> > information, and there is no automatic object reference collection
support
> > in TPTP.
> > After you perform a collect object reference action, please refresh the
> > Object Reference view to show the most updated information. Please note
that
> > Object Reference view can shown either 'Reference To' or 'Reference By'
> > orientation, via the drop down button of the view toolbar.
> >
> > Hope this help.
> > Eugene
> >
> > "Francis Upton" <francisu@ieee.org> wrote in message
> > news:dcn41c$n8m$1@news.eclipse.org...
> >
> >>I figured out how to get the object references; apparently you have to
> >>do this while the test is running. Is this the only way to do this?
> >>Can it be set up to automatically collect the references?
> >>
> >>Is there a way to get a stack trace associated with the references (like
> >> what hat can do?).
> >>
> >>Thanks,
> >>
> >>Francis
> >>
> >>Francis Upton wrote:
> >>
> >>>Hi,
> >>>
> >>>I am using TPTP 4.0.0 to try and find a memory leak which shows up
after
> >>>a long time of running tests.
> >>>
> >>>I can see one class of object that has more than the number of expected
> >>>instances, but I can't find out how to get the stack trace of where
> >>>these instances are allocated (or at least which objects point to these
> >>>instances).
> >>>
> >>>I looked at the documentation that is around and see that enabling
> >>>instance level object collection should show at least some of this
> >>>information. I have tried to do that, but the number of references and
> >>>details columns in the object references view are consistently blank,
> >>>and each line of object reference never has subordinate objects.
> >>>
> >>>Is there something I am missing?
> >>>
> >>>Thanks,
> >>>
> >>>Francis
> >
> >
> >
|
|
|
Powered by
FUDForum. Page generated in 0.02804 seconds
Home