Memory Leak due to CurrentInstance / ThreadLocal ?

Vaadin 6 / 7 / 8
1

Hi there,

we have Vaadin 7 running in a Tomcat environment. We´re using the default heartbeat mechanism and a Tomcat session timeout of 5 minutes:

	
<session-config>
	<session-timeout>5</session-timeout>
</session-config>

Nevertheless, we can´t get rid of some (not all) UI instances, even after several days. Please have a look this gc root path from a heap dump - “AdSuite5” is our UI subclass.

Is this a Vaadin bug? What would be the right way to cope with this?

Thanks,
Stefan
12860.png

2

No one? No idea?

@Vaadin team: Should I file a ticket for this, or am I simply missing something very basic?

Stefan

3

Hi Stefan,

It seems to be a bug in the framework and I’m now starting to look at it (http://dev.vaadin.com/ticket/12401).

/Jonatan