Destroying an 'offscreen FBO GLAutoDrawable' may crash on described machine/driver, due to double-free of pending resources (driver bug). This seems to be related to the performing thread's lifecycle, and JOGL's initialization (GLProfile.initSingleton()) may influence this issue (when and from which thread). The 'offscreen FBO GLAutoDrawable' only differs from others by its performing thread .. and its 'early usage'. If skipping its usage (manual probing), later on usage of 'offscreen FBO' seem to work as expected. A workaround is to not destroy this manual 'offscreen FBO GLAutoDrawable', or do keep its operating thread alive. The latter methodology is utilized by JOGL's own initialization to avoid driver issues. More details will follow ..
Not Working (crash): Version: 4.0.0 - Build 9.18.10.3220 Vendor: Intel^M Renderer: Intel(R) HD Graphics 4400 Driver is from 7/23/2013 (lenovo website) I could reproduce this issue once using a friends laptop, which is to no avail anymore. +++ Working: Version: 4.3.0 - Build 10.18.14.4264 Vendor: Intel Renderer: Intel(R) HD Graphics 4600 Driver is 15.36.23.4264 (10.18.14.4264) from win64_153624.exe. +++ - No crash found w/ current Intel driver. - Determined to be a driver issue - Workaround: - Install new driver - or - - Don't destroy the offscreen drawable then :-/ We could add a quirk for this specific renderer, assuming the versions < 10 may cause the issue. However, this is pretty vague.
Additional note, working machine: - Windows 8.1 64bit - Java 1.8.0_60 64bit - GPU Intel: Version: 4.3.0 - Build 10.18.14.4264 Renderer: Intel(R) HD Graphics 4600 Passed all unit tests of current JOGL master/commit d3db8fc5f03f280cef0d485b93dc8de5a2db9399