Posted by Archie on Sep 26, 2011; 3:37pm
URL: https://forum.jogamp.org/Crashing-with-GLCanvas-need-help-tp2579645p3369594.html

It seems like I have encountered a similar problem.  Though I am experiencing this with a recent official build:
jogamp-windows-amd64.7z (v2.0-rc3)

The code I wrote is just some basic code to set up a a GLCanvas and draw a quad on it (leolol setup tut).   It actually works the first few times I run it.  But after a while I start getting the error message that I have pasted below.  If I restart my computer and run this program again it works for the next dozen or so runs and then goes to the same exception again and keeps throwing that same exception.

If I change the GLCanvas to a GLJPanel (like someone suggested) instead it seems to circumvent the bug..

Here is the code I was running:
http://pastebin.com/90HSjfBu

I am running on Eclipse Indigo
Java 1.6 Update 26
Project is set up as Java 6.
OS: Windows 7 (64 bit)
Graphics Card: 8800 GTS - Driver: 8.17.12.5896 (Date: 9/07/2010)
Note: This is a dual display card with two monitors in use. (Not a dual card setup)
Processor: Q6600
Ram: 4gb

Here is the exception:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000000bbbbe4b, pid=1248, tid=6984
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [nvoglv64.DLL+0x71be4b]
#
# An error report file with more information is saved as:
# C:\Users\Mark\Dropbox\dev\jSpace\personal\JOGLsamples\hs_err_pid1248.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#