Hey Wolfgang, I've been happily using your component as we undertook migrating our Vaadin 7 application through to Vaadin 14 over the last year or so.
We just recently though started looking at Production migration, and our performance testing is pointing to a memory leak from the GridBagLayout.
It appears the GridBagLayout is resulting in browser JVM memory leaking, with HTML elements resulting in Detached state after removal, with active memory references. This occurs even just having an instance on a page without content.
Has anything like this been noticed?
I saw your comment to Andre previously about the internal repository, so I realise I cannot investigate myself.
Just thought I'd start the discussion here, while I try and find a way around this.
So far it seems as easy as just adding a GridBagLayout to a screen. Even if it's empty with no content.
Using Edge Browser -> developer tools, the Detached Elements tool. (to easily view detached elements, can see it in Dev Tools for Chrome too, but Edge has the easily used tool that makes it a little faster).
When you open up your application, and then navigate to the View that has the GridBagLayout in it, then browse away from that screen.
Repeat this a few times. Navigating to/from the view with the component in it.
Examine the list of detached elements in your dev tools for the browser.
You'll see the layout that contained the GridBagLayout will be 'detached' with memory reference still alive. There'll be as many detached as there were navigations to/from that page.
For our application, many of our pages have many Components under the GridBagLayout. So after repeating this kind of test, we were seeing the browser JVM climbing easily to above 100MB after say 10 repitiions of this testing.
In testing, I removed the Grid Bag Layout and put a Vaadin core FormLayout in it's place, and immediately all the detached elements and memory leaks disappeared.