You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org> on 2005/05/26 21:08:58 UTC
[jira] Created: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
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
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=comments#action_66391 ]
Faizan Ahmed commented on XALANJ-2128:
--------------------------------------
There is no guarantee that finalizers will be executed promptly. It can take arbitrarily long between the time that an object becomes unreachable and the time that its finalizer is executed.
The promptness with which finalizers are executed is primarily a function of the garbage collection algorithm, which varies widely from JVM implementation to JVM implementation. The behavior of a program that depends on the promptness of finalizer execution may likewise vary. It is entirely possible that such a program will run perfectly on the JVM on which you test it and then fail miserably on the other JVM.
Tardy finalization is not just a theoretical problem. Providing a finalizer for a class can arbitrarily delay reclamation of its instances.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Resolved: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Henry Zongaro (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=all ]
Henry Zongaro resolved XALANJ-2128:
-----------------------------------
Fix Version: CurrentCVS
Resolution: Fixed
This problem was fixed in CVS by Igor Hersht. I don't think Igor ever opened a bug report for this problem. The fix will be included in the Xalan-J 2.7.0 release.
> 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
> Fix For: CurrentCVS
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=comments#action_12355774 ]
Faizan Ahmed commented on XALANJ-2128:
--------------------------------------
Brian,
I have done testing with the Xalan-J 2.7 and ran every Scenario related to this issue to find the memory leak. I did not find any leak rlated to this issue. I confirm this issue has been fixed for Xalan-J 2.7. You can close this issue.
Thanks.
Faizan
> 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
> Fix For: 2.7
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=comments#action_12319253 ]
Brian Minchau commented on XALANJ-2128:
---------------------------------------
Faizan,
Xalan-J 2.7 was released on Aug 8, 2005. Please confirm that the memory leak is fixed in the 2.7 release, and we can then close this issue.
Thanks.
> 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
> Fix For: 2.7
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=all ]
Faizan Ahmed updated XALANJ-2128:
---------------------------------
Attachment: XRTreeFrag_RetainedObjects.jpg
XRTreeFrag_RetainedObjects represents all the objects retained in memory only because of XRTreeFrag Objects.
> 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_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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=all ]
Faizan Ahmed updated XALANJ-2128:
---------------------------------
Attachment: XRTreeFrag_GCRoots_2.jpg
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=comments#action_12319382 ]
Faizan Ahmed commented on XALANJ-2128:
--------------------------------------
Brian,
I will do by the end of next week (08/26/2005) and I will let you guys know.
Thanks.
> 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
> Fix For: 2.7
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2128?page=all ]
Brian Minchau updated XALANJ-2128:
----------------------------------
Fix Version: 2.7
(was: CurrentCVS)
> 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
> Fix For: 2.7
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2128) Finalizer in XRTreeFrag (xalan.jar) causes lots of loitered objects (memory leak).
Posted by "Faizan Ahmed (JIRA)" <xa...@xml.apache.org>.
[ 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org