I am using jogl-2.0-b327-20110225-windows-i586
package gldemo; import java.awt.BorderLayout; import javax.media.opengl.GLCapabilities; import javax.media.opengl.GLProfile; import javax.media.opengl.awt.GLCanvas; import javax.swing.JFrame; public class Main { public static void main(String[] args) { GLProfile.initSingleton(true); GLProfile profile = GLProfile.getDefault(); GLCapabilities capabilities = new GLCapabilities(profile); GLCanvas canvas = new GLCanvas(capabilities); JFrame frame = new JFrame(); frame.setSize(320, 240); frame.setVisible(true); frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE); // Crash here frame.getContentPane().add(canvas, BorderLayout.CENTER); } } That´s my code, it generates a log file : # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x69b5c430, pid=188, tid=3256 # # JRE version: 6.0_22-b04 # Java VM: Java HotSpot(TM) Client VM (17.1-b03 mixed mode, sharing windows-x86 ) # Problematic frame: # C [nvoglv32.DLL+0x65c430] # # An error report file with more information is saved as: # C:\Users\Gus7\Documents\NetBeansProjects\GLDemo\hs_err_pid188.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. # Can you help me, this code used to work |
Administrator
|
On Saturday, February 26, 2011 02:29:32 bardackx [via jogamp] wrote:
> I couldn't reproduce the crash here, kubuntu-nvgtx40 latest drivers/source, please retry with latest builds. +++ Please be so kind and follow http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testing so we are able to help you. at least send us the above mentioned information, if you don't like to add a bugreport right away. ~Sven > package gldemo; > > import java.awt.BorderLayout; > import javax.media.opengl.GLCapabilities; > import javax.media.opengl.GLProfile; > import javax.media.opengl.awt.GLCanvas; > import javax.swing.JFrame; > > public class Main { > > public static void main(String[] args) { > GLProfile.initSingleton(true); > GLProfile profile = GLProfile.getDefault(); > GLCapabilities capabilities = new GLCapabilities(profile); > GLCanvas canvas = new GLCanvas(capabilities); > > JFrame frame = new JFrame(); > frame.setSize(320, 240); > frame.setVisible(true); > frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE); > > // Crash here > frame.getContentPane().add(canvas, BorderLayout.CENTER); > } > } > > That´s my code, it generates a log file : > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x69b5c430, pid=188, > tid=3256 > # > # JRE version: 6.0_22-b04 > # Java VM: Java HotSpot(TM) Client VM (17.1-b03 mixed mode, sharing > windows-x86 ) > # Problematic frame: > # C [nvoglv32.DLL+0x65c430] > # > # An error report file with more information is saved as: > # C:\Users\Gus7\Documents\NetBeansProjects\GLDemo\hs_err_pid188.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. > # > > _______________________________________________ > If you reply to this email, your message will be added to the discussion below: > http://forum.jogamp.org/Crashing-with-GLCanvas-need-help-tp2579645p2579645.html > To start a new topic under jogl, email [hidden email] > To unsubscribe from jogl, visit health & wealth mailto:[hidden email] ; http://jausoft.com land : +49 (471) 4707742 ; cell: +49 (151) 28145941 Timezone CET: PST+9, EST+6, UTC+1 |
Am using the lastest build (today´s), since it appears to be a problem only on my computer ¿Is it normal that GLWindow dont call the windowDestroyNotify from an added WindowListener?
PD: I am going to find out how to fill a bug report |
Administrator
|
On Saturday, February 26, 2011 02:53:46 bardackx [via jogamp] wrote:
> > Am using the lastest build (today´s), since it appears to be a problem only > on my computer Or on your setup .. somehow. > ¿Is it normal that GLWindow dont call the windowDestroyNotify > from an added WindowListener? You mean NEWT ? Yes .. this bug is still to be fixed, if you refer to window close via mouse/UI, and 'nothing happens' .. > > PD: I am going to find out how to fill a bug report That would be awesome, plus the information provided will help us to identify the issue you have. ~Sven |
Whe I was trying to fill my bug report I found this:
https://jogamp.org/bugzilla/show_bug.cgi?id=469 It is basically the same issue. And the setting -Djogl.debug=true causes the application to run correctly |
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. # |
I should also add that although this bug happens on my desktop listed above. It does not seem to happen on my laptop (I have only tested it with a single screen display). The laptop is running windows 7 and the same version of eclipse. The Java version on the laptop is 1.6 Update 18
Please forgive me If you are already aware of this bug in the recent build. But do let me know where I can find out more about it if you have been working on it. Mark |
Administrator
|
It should work with the latest dev build. Please give it a try and tell us if everything is ok.
Julien Gouesse | Personal blog | Website
|
I couldn't work out how to get access to any build later than b485 which I found here:
http://jogamp.org/deployment/autobuilds/master/jogl-b485-2011-09-20_08-30-36/ As I was hooking eclipse into this build I noticed that glue gen was no longer present in the lib folder. I only had a Jar for glue gen in the atomic folder. So without gluegen it seems my project cannot even run. So at this stage I got glue-gen from a previous release and referenced that. I get the feeling that this is probably not wise. Anyway the project ran again but I still get that same bug I am talking about. If I have totally stuffed up the process of trying the latest dev build. please let me know how I should go about doing this properly. Thanks guys! |
Ah, nevermind, I found the latest build (b490) but I can still see that there is no gluegen file in the lib folder like there used to be in the V2.0 rc3 release. What should I do about gluegen? |
Administrator
|
Take the most recent GlueGen build which is in a separate folder but in the "dev build" section.
Julien Gouesse | Personal blog | Website
|
Ok, I have the most recent gluegen and the most recent jogl setup properly now. jogl-2.0-b492-20110927-windows-amd64.7z gluegen-2.0-b413-20110927-windows-amd64.7z I ran the same code that I was having trouble with before and I still get the same, EXCEPTION_ACCESS_VIOLATION The details of my system and the exact code I used are above. I can supply more if you require. Any ideas? |
Free forum by Nabble | Edit this page |