Posted by wspear on Apr 18, 2013; 6:25pm
URL: https://forum.jogamp.org/After-upgrading-from-JOGL1-my-canvas-dies-when-moving-between-monitors-tp4028978p4028982.html

A quick update: Digging in with some simpler examples it looks like the renderer by itself isn't the problem. The dispose call is coming from higher up in the UI stack. Unless the dispose call arrives when dragging between windows this issue will  not occur and that only happens with my full application, not my little canvas-only test cases.

I'm still trying to figure out what part of my UI is sending dispose on a monitor switch. executeDisplayChangedOnEDT in AWT's XWindowPeer class calls the awt.component's setGraphicsConfiguration and this is what leads to the dispose but all of that is fired off in its own thread and I can't tell where in my UI code it's coming from via the stack trace.