[ grinder-Bugs-3406177 ] Instrumented objects are not garbage collected

Bugs item #3406177, was opened at 2011-09-08 11:47
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3406177&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core engine
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://me.yahoo.com/a/HrlxAKkG ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Instrumented objects are not garbage collected

Initial Comment:
I'm created a new instrumented object every Grinder run and eventually running out of tenured heap space in my JVM on extended soak tests.

>From Phil:

Each instrumented object uses memory to bind the instrumentation to the appropriate Test - a reasonable requirement. Unfortunately, The Grinder does not tidy up this memory if an instrumented object is garbage collected, and so instrumenting an object and throwing it away is an effective memory leak. Further, it will maintain a strong reference to the target object, pinning it in memory too.

Each instrumentation point in an object uses a CopyOnWriteArrayList, and hence a RentrantLock. This can be seen in an allocation stack trace (attached).


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3406177&group_id=18598

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/