Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » Unreleased memory usage after profiling

Show: Today's Messages :: Show Polls :: Message Navigator

Unreleased memory usage after profiling [message #139550]

Wed, 14 January 2009 19:08

Gabriel Valencia

Messages: 16
Registered: July 2009

Junior Member

I am using TPTP 4.5.1 with Eclipse 3.4.1 on Win XP Pro SP2. I notice that
after executing a profiling session (gathering execution statistics), the
heap usage in Eclipse goes up and the memory isn't released with garbage
collection. Therefore, I can only run 1 or 2 (maybe 3) profiling sessions
before I start getting out of memory errors in Eclipse and have to restart
the workbench.

Is this expected behavior? I'm already at 650 MB of heap, don't think I
can go much higher with the amount of RAM I have.

Thanks for reading.

Report message to a moderator

Re: Unreleased memory usage after profiling [message #140013 is a reply to message #139550]

Thu, 05 February 2009 22:15

Eugene Chan

Messages: 287
Registered: July 2009

Senior Member

Hi Gebriel,

There is an action available under the 'Profiling Monitor' view named
'Unload Profiling Data' that enables user to free up the memory used for
profiling data collected. Select an profiling agent for example and right
click for the context menu for the action. When selected, you will be
prompted with an option to save the resource to file as needed before the
data is released from memory, in case you would like to reload the profiling
data later. Keep in mind that you will not be able to view any unsaved data
at a later time.

Eugene

"Gabriel Valencia" <gvalenc@us.ibm.com> wrote in message
news:0d546a370a988fb64f136be337734513$1@www.eclipse.org...
>I am using TPTP 4.5.1 with Eclipse 3.4.1 on Win XP Pro SP2. I notice that
>after executing a profiling session (gathering execution statistics), the
>heap usage in Eclipse goes up and the memory isn't released with garbage
>collection. Therefore, I can only run 1 or 2 (maybe 3) profiling sessions
>before I start getting out of memory errors in Eclipse and have to restart
>the workbench.
>
> Is this expected behavior? I'm already at 650 MB of heap, don't think I
> can go much higher with the amount of RAM I have.
>
> Thanks for reading.
>

Report message to a moderator

Previous Topic:	OC4J and Agent Controller
Next Topic:	AGR and continous integration

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 12:18:04 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter