Bug 1204 - Crash on Windows w/ Intel Driver Version or 9.18.xx while destroying offscreen FBO GLAutoDrawable
Summary: Crash on Windows w/ Intel Driver Version or 9.18.xx while destro...
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 2.3.2
Hardware: All windows
: --- major
Assignee: Sven Gothel
Depends on:
Reported: 2015-08-27 20:37 CEST by Sven Gothel
Modified: 2015-09-27 01:11 CEST (History)
1 user (show)

See Also:
Type: ---
SCM Refs:
Workaround: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2015-08-27 20:37:51 CEST
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 ..
Comment 1 Sven Gothel 2015-09-02 03:50:34 CEST
Not Working (crash):
    Version: 4.0.0 - Build
    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.


    Version: 4.3.0 - Build
    Vendor: Intel
    Renderer: Intel(R) HD Graphics 4600

Driver is (
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.
Comment 2 Sven Gothel 2015-09-02 03:54:32 CEST
Additional note, working machine:
 - Windows 8.1 64bit
 - Java 1.8.0_60 64bit
 - GPU Intel:
   Version: 4.3.0 - Build
   Renderer: Intel(R) HD Graphics 4600

Passed all unit tests of current JOGL
  master/commit d3db8fc5f03f280cef0d485b93dc8de5a2db9399