Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

Start an out of the box build. I used a wildfly-9.0.0.Alpha1-SNAPSHOT build of July 9th.

Run the attached standalone program. It will do a loop creating a connection, and destroying it (try-with-resources)

When it display 240.000 take a heap dump. The dump will contain an equal amount of ThreadGroup objects as connections have been made.

The program will show memory calculations. These are not very precise of course, but the heap dump is very clear.

Show
Start an out of the box build. I used a wildfly-9.0.0.Alpha1-SNAPSHOT build of July 9th. Run the attached standalone program. It will do a loop creating a connection, and destroying it (try-with-resources) When it display 240.000 take a heap dump. The dump will contain an equal amount of ThreadGroup objects as connections have been made. The program will show memory calculations. These are not very precise of course, but the heap dump is very clear.
Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/35
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1120177

org.jboss.as.controller.client.impl.ClientConfigurationImpl

052 static ExecutorService createDefaultExecutor() {
053 final ThreadGroup group = new ThreadGroup("management-client-thread");

The ThreadGroup is never cleaned up and creates a memory leak