Issue2132

Terminating a modjy-Webapp within Tomcat causes a mermory leak on the server.

The problem can be easily reproduced with the modjy-webapp demo from the jython repository: Deploy the app, stop the app.

It's the same behaviour described in the mailinglist-post [1].

Profiling Tomcat after stopping the app, according to guide [2] shows, that the main reason for the leak could be an instance of "RefReaperThred". This issue could also correspond to issue 2127 [3].

I verfied this problem within several Tomcat versions under Linux and Windows with Jython 2.5.3 and Jython 2.7.b1.


[1] Jython User-Mailinglist post "How can I shut down Jython cleanly?": http://sourceforge.net/p/jython/mailman/message/29044817/

[2] Anatomy of a PermGen Memory Leak: http://cdivilly.wordpress.com/2012/04/23/permgen-memory-leak/

[3] Jython Issue 2127: http://bugs.jython.org/issue2127

There was also an IRC discussion corresponding to this problem: http://www.extreme.st/jython.extreme.st/irclogs/index.php?date=2013-10-02

Looks like we need to fix the underlying problem in #2127

Duplicate of #2127

#2127 was recently fixed

Unfortunately the bug still occurs.

I've tested the Modjy demo webapp with the current repository versions of Jim Baker[1] and Jython [2]. After undeploying the app via the Tomcat manager resources are still locked. VisualVM points to the ApplicationShutdownHook.

Am I doing something wrong? Has anyone a war-example which can be stopped / undeployed without memory leaks? 

[1] https://bitbucket.org/jimbaker/jython-resource-leaks/get/6d3e8e67af1d.zip
[2] https://bitbucket.org/jython/jython/get/a00987ea4da6.zip