Login  Register

Win7 64 run-time native code error during Java3D app launch

Posted by pbierre on Apr 16, 2016; 11:25pm
URL: https://forum.jogamp.org/Win7-64-run-time-native-code-error-during-Java3D-app-launch-tp4036604.html

I'm converting my Win7 Java3D app from Oracle JRE 1.8.0_25 to 1.8.0_77 (Java3D jars not bundled).   I'm using the Eclipse Mars2.0 IDE.  The compiler is happy, so it's finding all the JOGL jars.

When I launch my app, you see the app window for about 1/4 sec. duration, then it disappears.   This is the pid report
coming up from the .dll layer.  It's something about "Minidumps are not enabled by default on client versions of Windows"

Possible clue: I'm running Win 7 on a Macbook Pro (Intel 2-core) under Parallels Desktop 10.   Could there be a problem
with compatibility of JOGL's native amd-64 driver with the Intel GPU?   Is there a hardware-compatibility test I can run?  
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fef0ea34d9, pid=5032, tid=1496
#
# JRE version: Java(TM) SE Runtime Environment (8.0_77-b03) (build 1.8.0_77-b03)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.77-b03 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [prl_gldd.dll+0x134d9]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\pbierre\workspaceJogAmpWin7\AlgoGeom3D\hs_err_pid5032.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Has anyone experienced this problem?   Any ideas how to solve it?  I was expecting JOGL to provide a turnkey solution.