Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Profiling Crash/Mem leak not seen?
Profiling Crash/Mem leak not seen? [message #20265] Thu, 16 June 2005 03:07 Go to next message
Eclipse UserFriend
Originally posted by: lbmes2000.yahoo.com

Hi all

Im using tptp 4.0. When I start memory profiling everything works fine --
i am able to call up instance info and whatnot. After a number of
refreshes, however, the memory profiler claims there is no info and I have
to start recollecting info, losing all the previosly gathered info.
Eventually both eclipse and the program suffer OutOfMemoryError meessages.
While the profiler is working, it does not appear that the program is
leaking memory, the number of live instances for any particular class does
not grow. I get the OOM for the application when I run it from the
command line as well. I am running under linux. I am not clicking the
option that warns about exponential memory growth (instance level info),
and I do not have any limits set. Here is what shows up on the command
line when eclipse collapses.

java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Unhandled event loop exception
Reason:
Failed to execute runnable (java.lang.OutOfMemoryError)
*** SWT nested exception
Reason:
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Re: Profiling Crash/Mem leak not seen? [message #20293 is a reply to message #20265] Fri, 24 June 2005 07:26 Go to previous message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Hi Michael,

There is a possibility that you are filtering out the type of instance that
causes the OOM. Check your filters under the profiler to ensure that you
are not filtering possible candidates that maybe causing the OOM.
You can adjust your filter under the profiler launcher > Profiling tab >
Select the desired profiling set > Click Edit > Next > Next > You can set
your filter set under this page

Sorry for the delay in response.


"Michael Harris" <lbmes2000@yahoo.com> wrote in message
news:affada3243a6dd210647e28f426b2994$1@www.eclipse.org...
> Hi all
>
> Im using tptp 4.0. When I start memory profiling everything works fine --
> i am able to call up instance info and whatnot. After a number of
> refreshes, however, the memory profiler claims there is no info and I have
> to start recollecting info, losing all the previosly gathered info.
> Eventually both eclipse and the program suffer OutOfMemoryError meessages.
> While the profiler is working, it does not appear that the program is
> leaking memory, the number of live instances for any particular class does
> not grow. I get the OOM for the application when I run it from the
> command line as well. I am running under linux. I am not clicking the
> option that warns about exponential memory growth (instance level info),
> and I do not have any limits set. Here is what shows up on the command
> line when eclipse collapses.
>
> java.lang.OutOfMemoryError
> java.lang.OutOfMemoryError
> Unhandled event loop exception
> Reason:
> Failed to execute runnable (java.lang.OutOfMemoryError)
> *** SWT nested exception
> Reason:
> java.lang.OutOfMemoryError
> java.lang.OutOfMemoryError
>
>
Previous Topic:TPTP and CDT links
Next Topic:how to work with rich-Client Application?
Goto Forum:
  


Current Time: Mon Dec 22 22:54:20 GMT 2014

Powered by FUDForum. Page generated in 0.01569 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software