[ http://issues.apache.org/jira/browse/XALANJ-2128?page=all ]
Faizan Ahmed updated XALANJ-2128:
---------------------------------
Attachment: XRTreeFrag_GCRoots_1.jpg
XRTreeFrag_GCRoots_1 reflects why XRTreeFrag is getting blamed.
> Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory
> leak).
> ----------------------------------------------------------------------------------
>
> Key: XALANJ-2128
> URL: http://issues.apache.org/jira/browse/XALANJ-2128
> Project: XalanJ2
> Type: Bug
> Components: Xalan
> Versions: 2.6
> Reporter: Faizan Ahmed
> Attachments: XRTreeFrag_GCRoots_1.jpg, XRTreeFrag_GCRoots_2.jpg,
> XRTreeFrag_RetainedObjects.jpg
>
> Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects. Since
> there is a clean up method destruct() available and all the clients should
> call this clean up method rather rely on finalizer.
> Because of finalizer in this class these objects gets put on finalizer queue
> and dont get cleaned when they go out of scope. Finalizer is provided
> probably as a safty net here but this is hurting swearly.
> The fix should be simple remove finalizer from this class. I have tested it
> and it did clean up the resources and fix the memory leak.
> The attached snapshots should help to explain this fact (both leaked Objects
> and after the fix no memory leak because of XRTreeFrag).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
