|Process Memory size grows fast even when profiler is in the pause mode [message #108083]
||Wed, 08 August 2007 19:15
Registered: July 2009
I am trying to get an execution flow information for our application. First
I was trying to run it in the "enabled" control mode like so:
But this does not seem to work and one of the bugs states that it is not
possible to get an execution flow information with JVMTI profiler in
"enabled" mode since profiler does not know complete context by the time it
connects to the application.
So I was trying to run the application in "controlled" mode and pause the
collecting of the profiling data until i am ready to execute a use case. But
what I am seeing is that memory that is occupied by my application process
grows very rapidly and quickly reaches 1.5GB or so and then I am getting out
of memory exception. My application's heap size is maxed at 512 so i am
possitive that it is a native part of the profiler that occupies all the
I am wondering what kind of information is it storing that it takes up so
much space considering profiling is on pause. Is all this "context"
information taking up so much space? Can someone explain?
Powered by FUDForum
. Page generated in 0.02703 seconds