Bug 932

Hi

This is not reproducible with Intel HD Graphics 3000 for sure, another user asked me to fix a bug in Ardor3D JOGL 2 renderer and he tested under Windows 7 with this chip and an updated driver.

Do you experience similar crashes with OpenGL applications not using JOGL?

(In reply to comment #1)
> This is not reproducible with Intel HD Graphics 3000 for sure, another user
> asked me to fix a bug in Ardor3D JOGL 2 renderer and he tested under Windows
> 7 with this chip and an updated driver.

to be clear: a machine must have its display drivers poorly configured to exhibit this bug.  for this one machine under my control (and for many of our users) this poor state is the default configuration for the intel driver.

> Do you experience similar crashes with OpenGL applications not using JOGL?

on the machine configuration that exhibits this crash with jogl2, jogl v1.1.1 is able to create a GLPanel and render a complex scene.

jogl v1.1.1 is far from rock solid as it crashes when attempting to show two render windows.

> on the machine configuration that exhibits this crash with jogl2, jogl
> v1.1.1 is able to create a GLPanel and render a complex scene.

GLJPanel? Please can you enable all logs?
http://jogamp.org/wiki/index.php/Jogl_FAQ#Detailed_Debug_Log

The GDI renderer seems to be picked according to the outputs.

What happens if you call GLCapabilities.setDepthBits(24)?

Created attachment 573 [details]
detailed bug log requested by Julien Gouesse

see associated hs_err_pid4744.log

Created attachment 574 [details]
crash log associated with test_dbg

crash log when running test_dbg.bat

(In reply to comment #3)
> > on the machine configuration that exhibits this crash with jogl2, jogl
> > v1.1.1 is able to create a GLPanel and render a complex scene.
> 
> GLJPanel? Please can you enable all logs?
> http://jogamp.org/wiki/index.php/Jogl_FAQ#Detailed_Debug_Log

please see attachments 573 and 574.

test_dbg.bat crashes (as expected) but produces logs.

(In reply to comment #4)
> The GDI renderer seems to be picked according to the outputs.
> 
> What happens if you call GLCapabilities.setDepthBits(24)?

the following program:

javax.media.opengl.GLProfile glProfile = javax.media.opengl.GLProfile.getDefault();
javax.media.opengl.GLCapabilities glCapabilities = new javax.media.opengl.GLCapabilities(glProfile);
glCapabilities.setDepthBits(24);
javax.media.opengl.awt.GLCanvas glCanvas = new javax.media.opengl.awt.GLCanvas( glCapabilities );
javax.swing.JFrame frame = new javax.swing.JFrame();
frame.getContentPane().add(glCanvas);
frame.setVisible(true);

crashes on the very first line:

javax.media.opengl.GLProfile glProfile = javax.media.opengl.GLProfile.getDefault();

is there another way to test setting the depth bits that i am missing?
or were you asking me to test things on jogl v1.1.1?

Created attachment 578 [details]
JOGL's Version Applet output from 2 Machines w/ Intel HD3000 and HD4000

Intel(R) HD Graphics 3000
3.1 (Compat profile, arb, FBO, hardware) - 3.1.0 - 
Build 9.17.10.3347 [GL 3.1.0, vendor 9.17.10 (- Build 9.17.10.3347)]

Intel(R) HD Graphics 4000
4.0 (Compat profile, arb, ES2 compat, FBO, hardware) - 4.0.0 - 
Build 10.18.10.3345 [GL 4.0.0, vendor 10.18.10 (- Build 10.18.10.3345)]

Your crash w/
  Intel(R) HD Graphics 4600
  Driver Version: 10.18.10.3345

My working w/ (See Comment 9)
  Intel(R) HD Graphics 4000
  4.0 (Compat profile, arb, ES2 compat, FBO, hardware) - 4.0.0 - 
  Build 10.18.10.3345 [GL 4.0.0, vendor 10.18.10 (- Build 10.18.10.3345)]

Same driver, diff hardware .. hmm.

(In reply to comment #10)
> Your crash w/
>   Intel(R) HD Graphics 4600
>   Driver Version: 10.18.10.3345
> 
> My working w/ (See Comment 9)
>   Intel(R) HD Graphics 4000
>   4.0 (Compat profile, arb, ES2 compat, FBO, hardware) - 4.0.0 - 
>   Build 10.18.10.3345 [GL 4.0.0, vendor 10.18.10 (- Build 10.18.10.3345)]
> 
> Same driver, diff hardware .. hmm.

Since I don't have a HD4600 available, please test w/ 
the [following] latest driver and report, THANK YOU!

+++
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23405

Version: 15.33.8.64.3345 	
Date: 11/20/2013 	
Status: Latest 
+++

Reduced severity to 'major'.

Can we confirm this is a driver bug ?
After all .. this is very likely, since such call shall not cause a crash.

However, do we need a workaround or does the new Intel driver
fix the issue ?

I like to pressure this resolution for the 2.1.4 release,
again - sadly I don't have a box w/ this configuration.

Anybody willing to give me ssh access to such ?

Created attachment 579 [details]
JOGL Version Applet main output for Intel 4600 w/ well configured drivers

Created attachment 580 [details]
JOGL Version Applet capabilities output for Intel 4600 w/ well configured drivers

(In reply to comment #11)
> (In reply to comment #10)
> > Your crash w/
> >   Intel(R) HD Graphics 4600
> >   Driver Version: 10.18.10.3345
> > 
> > My working w/ (See Comment 9)
> >   Intel(R) HD Graphics 4000
> >   4.0 (Compat profile, arb, ES2 compat, FBO, hardware) - 4.0.0 - 
> >   Build 10.18.10.3345 [GL 4.0.0, vendor 10.18.10 (- Build 10.18.10.3345)]
> > 
> > Same driver, diff hardware .. hmm.
> 
> Since I don't have a HD4600 available, please test w/ 
> the [following] latest driver and report, THANK YOU!
> 
> +++
> https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23405
> 
> Version: 15.33.8.64.3345 	
> Date: 11/20/2013 	
> Status: Latest 
> +++

the results of the JOGL's Version Applet can be found in attachment 579 [details] and attachment 580 [details].

(In reply to comment #12)
> Reduced severity to 'major'.
> 
> Can we confirm this is a driver bug ?
> After all .. this is very likely, since such call shall not cause a crash.
> 
> However, do we need a workaround or does the new Intel driver
> fix the issue ?
> 
> I like to pressure this resolution for the 2.1.4 release,
> again - sadly I don't have a box w/ this configuration.
> 
> Anybody willing to give me ssh access to such ?

There has never been any question in my mind that this is a bad driver configuration problem.  There are many ways to fix this problem: download the latest drivers from Intel -or- go the the Performance Information And Tools control panel and click on a button -or- run winsat.exe...  

Why this issue is so critical to me is that the driver problem we are triggering does not throw and exception, it *crashes*.  I know it is not anyone on the JOGL team's fault, but I'm hoping we can find some clever way to detect and avoid this crash.  The Intel cards are pervasive and a lot of our users report this problem.  More scary is the fact it happens on my newly minted Windows 7 machine (even after completely Windows Updating).  Sadly, not all of our users have the technical expertise or even the permissions to install new drivers.

If we cannot come up with a solution, my current plan is to record the fact that initSingleton did not return and on the next run of the system prompt with a fix-your-graphics-drivers dialog that runs winsat.exe.  Still, I hold out hope we might be able to detect something is awry and respond accordingly.

Thank you for all of your work on JOGL.

(In reply to comment #12)
> Anybody willing to give me ssh access to such ?

I am happy to do whatever it takes to help solve this problem.

P3 normal - ANNOTATION - Workaround (desired),

since we agree it's an Intel GPU driver bug.

(In reply to comment #17)
> (In reply to comment #12)
> > Anybody willing to give me ssh access to such ?
> 
> I am happy to do whatever it takes to help solve this problem.

@Dennis: Yes, that would be great.

http://jogamp.org/git/?p=jogamp-scripting.git;a=tree;f=jenkins-server-slave-setup/cygwin-sshd;h=43950cf6c6c499dbd7aab137c827c158e0f81ba0;hb=HEAD

We would need the 'usr process' setup, 
since we need access to the GPU, see:

- cygwin_sshd_win7_init.txt
- cygwin_sshd_win7_usr_process.txt

I have sent you my ssh public key via email.

+++

~Sven

windows deletes user created restore points in favor of insignificant automatic restore points.  this leaves me in a deep state of sadness and no longer able to reproduce the bug.