|Profiling Crash/Mem leak not seen? [message #20265]
||Thu, 16 June 2005 03:07
Originally posted by: lbmes2000.yahoo.com|
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.
Unhandled event loop exception
Failed to execute runnable (java.lang.OutOfMemoryError)
*** SWT nested exception
Powered by FUDForum
. Page generated in 0.01756 seconds