Memory Leak due to CurrentInstance / ThreadLocal ?

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:


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?


No one? No idea?

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


Hi Stefan,

It seems to be a bug in the framework and I’m now starting to look at it (