Memory leak in JR 3.7.3?

[lacito]

Dear developers,

We have developed a web application which uses JasperReports 3.7.3.

We use Tomcat 6.0.26 as a container. (Win XP, JDK 1.6.0_10)

We shutted down Tomcat, and we found the following messages in the catalina.log file:

SEVERE: A web application created a ThreadLocal with key of type [null] (value [net.sf.jasperreports.engine.util.JRFontUtil$1@19d373]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

 

It seems to be a leak.

Can you confirm it?

Thanks,

Laszlo Sas

[lucianc]

That type of leaks cause problems when the web application is stopped or redepolyed (without restarting Tomcat).  If you don't do that, there are no reasons to worry.

In any case, log it as a bug and we'll see what we can do about it.

Regards,

Lucian

[lacito]

Thank you for the fast answer! :)

 

Regards,

 

Laszlo

[xmedeko]

Hi,

I have fixed that, see

http://jasperforge.org/projects/jasperreports/tracker/view.php?id=4768

 

Unfortunatelly, there are more ThreadLocal memory leaks in JasperReports :-(

[xmedeko]

See http://jasperforge.org/projects/jasperreports/tracker/view.php?id=4882

 

Unfortunatelly, there are even more ThreadLocal memory leaks in JasperReports :-(

[xmedeko]

I have set

net.sf.jasperreports.evaluator.class.reference.fix.enabled=false

in the jasperreports.properties and now it is not, hopefully, leaking. i think there are more memory leaks in the code (e.g. http://jasperforge.org/projects/jasperreports/tracker/view.php?id=3084), but I just do not use this code.

[xmedeko]

Hmm, version 3.7.5 released and the memory leaks are not fixed there :-(

[xmedeko]

Hello JasperReports developers,

are you going to solve these redeploy memory leaks in JasperReports some day? May some financial contribution to your project encourage you to take interest in these nasty things? /tools/fckeditor/editor/images/smiley/msn/wink_smile.gif

I have already submitted two pathes fixing these memory leaks, but none of them has been accepted up to now (version 4.0.0). At least the BorderOffset patch is not breaking any original functionality.

I am asking epsecially to know If we can hope once these leaks will be solved or if we should change our deployment & release process to take into account and restart our server before each redeploy.

Thanks

Andy

[xmedeko]

I have found one more leak in SimpleFontExtensionHelper. If you make put SoftReference into the ThreadLocal then it is still memory leaking, since there is a circular reference! Furhemore, I if understand the code in net.sf.jasperreports.extensions.DefaultExtensionsRegistry.loadRegistries() - it right, then the SimpleFontExtensionHelper is initialized just once per class loader. So it is a nonses to cache its instances in ThreadLocal. Just create it, use it and forget it. No problems, no leaks.

[xmedeko]

Submitted bug http://jasperforge.org/projects/jasperreports/tracker/view.php?id=5164

[xmedeko]

I apologize, it seems that SimpleFontExtensionHelper was not a source of the leak in my application. The ThreadLocal->SoftReference just holds the undeployed application in the memory for a few minutes. (Which is not nice, anyway.)

No I have a probem with the sun.awt.AppContext.getAppContext() memory leak, since JasperReports uses awt fotnts to measure text width. Grrr, this bloody Java class loader hell.