United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-5073409 OGL: VM crash (SIGSEGV) on exit by ANY swing app on Nvidia 6106 drivers
JDK-5073409 : OGL: VM crash (SIGSEGV) on exit by ANY swing app on Nvidia 6106 drivers

Details
Type:
Bug
Submit Date:
2004-07-13
Status:
Closed
Updated Date:
2006-03-02
Project Name:
JDK
Resolved Date:
2004-11-10
Component:
client-libs
OS:
linux
Sub-Component:
2d
CPU:
x86
Priority:
P3
Resolution:
Not an Issue
Affected Versions:
5.0
Fixed Versions:

Related Reports

Sub Tasks

Description
Name: rmT116609			Date: 07/13/2004


FULL PRODUCT VERSION :
java version "1.5.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b51)
Java HotSpot(TM) Client VM (build 1.5.0-beta2-b51, mixed mode, sharing)


FULL OS VERSION :
Linux linux 2.6.5-7.75-Bivus #2 Fri Jun 25 18:07:11 GMT 2004 i686 i686 i386 GNU/Linux
Windows XP

EXTRA RELEVANT SYSTEM CONFIGURATION :
SuSE 9.1 Pro , TNT 2 video , NVIDIA-Linux-x86-1.0-6106-pkg1.run driver

A DESCRIPTION OF THE PROBLEM :
run a swing demo with OpenGL enabled:

java -Dsun.java2d.opengl=True -jar $JAVAHOME/demo/jfc/Notepad/Notepad.jar

The demo opens and is really broken.The gui is messed up.Menues don't repaint correctly.When I close the app I get:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x4662c9d2, pid=11318, tid=1167641520
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0-beta2-b51 mixed mode, sharing)
# Problematic frame:
# C  [libGLcore.so.1+0x2e69d2]  _nv000832gl+0x12
#
# An error report file with more information is saved as hs_err_pid11318.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted





STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
run the Notepad demo

java -Dsun.java2d.opengl=True -jar $JAVAHOME/demo/jfc/Notepad/Notepad.jar

Close the program.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Normal exit.
ACTUAL -
VM crash with SIGSEGV

ERROR MESSAGES/STACK TRACES THAT OCCUR :
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x4662c9d2, pid=11318, tid=1167641520
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0-beta2-b51 mixed mode, sharing)
# Problematic frame:
# C  [libGLcore.so.1+0x2e69d2]  _nv000832gl+0x12
#
# An error report file with more information is saved as hs_err_pid11318.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
$JAVAHOME/demo/jfc/Notepad/Notepad.jar - Shipped with the jdk1.5b2
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
use an older NVidia driver (NVIDIA-Linux-x86-1.0-5336-pkg1.run for example)
(Incident Review ID: 282334) 
======================================================================
###@###.### 10/25/04 23:49 GMT

                                    

Comments
EVALUATION

This appears to be a major regression in Nvidia's latest Linux drivers (6106).
We'll have to narrow this down into a native testcase and send it off to Nvidia
for review.
###@###.### 2004-07-14

This issue (app crash on exit with 6106/6111 drivers) has been fixed by
Nvidia in their latest (6629) driver release.  There does not appear to be
any way to workaround this problem in our OGL-based pipeline, so the only
way to resolve the problem is to upgrade to the 6629 drivers.  (There are
also performance improvements in the 6629 driver that are worth the upgrade.)
Once we've tested the new 6629 drivers on a few configurations and are
convinced that the issue is fixed, we will close this bug.
###@###.### 2004-11-09 21:03:53 GMT

I installed the new 6629 drivers on my JDS (Mercury) system (2x 2.6 GHz P4,
Nvidia GeForce FX 5600) and I am no longer able to reproduce the crash-on-exit
bug reported here, after trying a number of applications such as Java2Demo,
SwingSet2, etc.  I think we can safely say that the 6629 drivers fixed this
issue, so I will close this as "not a bug" (in the JDK, that is).
###@###.### 2004-11-10 22:56:53 GMT
                                     
2004-11-10



Hardware and Software, Engineered to Work Together