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

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.

pbierre,
I'm not an expert on the underlying driver side of things, but this problem was raised last year by the SweetHome3D developer;

https://forum.parallels.com/threads/cant-run-java-3d-1-6.328492/

and investigated by the jogamp team, for example
http://forum.jogamp.org/Java3d-1-6-0-pre12-released-requires-jogl-2-3-1-td4034327.html
and
https://bugs.mageia.org/show_bug.cgi?id=16280

Can you confirm what version of Java3D you are using? If it's not 1.6.0-pre12 then you'll need to update it.

Along with that you need to be using Jogl 2.3.2, which can be found here
http://jogamp.org/deployment/jogamp-current/archive/jogamp-all-platforms.7z
with info here
http://jogamp.org/wiki/index.php/Downloading_and_installing_JOGL#Downloading_the_latest_stable_version

In order to get some diagnostic information , if you download the 7z file linked above and extract it, in the root folder will be test.bat, please run that and reply with the output file (test.log) attached, this will show whether you are getting the same GDI driver issue described in the links at the top.

There are other people on the forum who know more about it than me, so they may have better advice to give.


Thanks,
Phil.

Phil, I'm using the correct Java3D jars....here's the launch banner when I run in MacOS:

3D [dev] 1.6.0-pre12-daily-experimental daily

I don't know how to launch "test.bat" under windows.   Whatever happened to the "cmd" launcher they had in WinXP?

Hi

Phil is right.

There is still "cmd" under Windows 7, 8 and 10. Search "Command Prompt" in the start menu or with Cortana. You can press Win+R and enter "cmd". Under Windows 7, open the start menu and go to "All Programs" -> "Accessories". Note that I'm not a Windows specialist, I'm mainly under Mageia Linux :)

AI extracted the entire "jogamp-all-platforms.7z" into a Win7 folder, and then ran the "test.bat" from the enclosed "etc" folder.

It terminated prematurely with this test.log:

Error: Could not find or load main class com.jogamp.newt.opengl.GLWindow

Sorry,
You did exactly the right thing, I forgot to mention a step.
The reason I said it would be in the root folder is actually because you have to move it there before it will run, I get the exact same unable to find... message if I run it in the etc folder, so please just move the test.bat file up one folder into the root folder (which will have jar as a sub folder) and then it should run.

Or if that doesn't work here is an alternative way to get the same information

Please run this program and post the result here:
http://jogamp.org/deployment/jogamp-current/jogl-application-version.jnlp

You may have to add jogamp.org to the exception list to run it:
https://www.java.com/en/download/faq/exception_sitelist.xml

THIS IS A PROBLEM WITH PARALLELS running Windows 7 on Mac hardware.   The problem goes away when running the exact same Eclipse Java Workspace that works on the Mac when ported onto a real Windows computer.

Jacques Gousse pointed out that the problem is that JOGAMP JOGL does not support or test virtualizations of the Windows OS run on foreign hardware.  Thanks, JG, good call.

I (Julien Gouesse) confirm that I said that there is a bug in Parallels, it crashes at the very first OpenGL call. Rather use Virtual Box.