You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2016/04/22 12:12:28 UTC

Memory leak progress report

Hi,

As I mentioned previously, I am working through the memory leak
detection and prevention code looking to see how it interacts with Java
9, particularly the restrictions placed on reflection.

I started with the RMI leak protection in WebappClassLoaderBase.

I have discovered from the OpenJDK devs[1] that there is a way that
applications can clean up after themselves which moves this leak to the
category of application error that should get a nice loud error message.
The problem is that there isn't a public API to identify what the leaks
are so generating those error messages - particularly in Java 9 - is
going to be tricky.

I have set up a GitHub repo [2] where I am creating sample apps to use
to explore the leaks that you might interesting.

Mark

[1]
http://mail.openjdk.java.net/pipermail/core-libs-dev/2016-April/040449.html
[2] https://github.com/markt-asf/memory-leaks

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org