commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olaf Tomczak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LANG-453) ToStringBuilder can cause serious memory leaks
Date Thu, 31 Jul 2008 17:20:32 GMT

    [ https://issues.apache.org/jira/browse/LANG-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618760#action_12618760
] 

Olaf Tomczak commented on LANG-453:
-----------------------------------

Thanks Gary. You're right - the object is unregistered - sorry for posting issue without investigating
it a little bit more. I was looking for memory leak in my application which uses Toplink JPA
and created a test case which proved that using toString() method before persisting my objects
caused them to stay on the heap forever. I'll try to isolate the problem and get back to you.

> ToStringBuilder can cause serious memory leaks
> ----------------------------------------------
>
>                 Key: LANG-453
>                 URL: https://issues.apache.org/jira/browse/LANG-453
>             Project: Commons Lang
>          Issue Type: Improvement
>    Affects Versions: 2.3
>         Environment: all
>            Reporter: Olaf Tomczak
>
> ToStringBuilder's constructor registers object passed as argument in thread local static
registry.  This causes serious memory problems in applications that run for a long time, use
thread pooling and process large amount of data (e.g. enterprise web applications). Each call
to toString method on an object causes this object to be practically impossible to garbage
collect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message