Summary: | VM crash with FATAL ERROR in native method: Nativewindow X11 IOError: Display ... | ||
---|---|---|---|
Product: | [JogAmp] Nativewindow | Reporter: | Pramod Patil <pramodd.patil> |
Component: | x11 | Assignee: | Sven Gothel <sgothel> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 2.4.0 | ||
Hardware: | All | ||
OS: | linux | ||
Type: | DEFECT | SCM Refs: | |
Workaround: | --- |
Description
Pramod Patil
2015-10-23 11:54:48 CEST
Please provide detailed information of your machine: <http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testing> i.e. the test_dbg.log, best to be compressed and attached here. Then we need a test case which is able to reproduce this issue, best if it is an already existing unit test of JOGL. Otherwise, pls write a unit test, a small piece of code, you may start using one of our unit tests. The issue is random and i am not able to reproduce it for second time. Its more about native method. For me it looks like display device was broken at that moment. I can provede the version of jogl which is : 2.1.3. It would be good if some one from NativeWindow can investigate on what might be the reason. (In reply to Pramod Patil from comment #2) > The issue is random and i am not able to reproduce it for second time. > Its more about native method. For me it looks like display device was broken > at that moment. I can provede the version of jogl which is : 2.1.3. It would > be good if some one from NativeWindow can investigate on what might be the > reason. Note: "Nativewindow X11 IOError: Display 0x9b6fc40 (:0.0): Broken pipe" indicated that the X11 display connection has been closed or is invalid. I cannot think of any case where this issue lies in our implementation. We need a simple standalone test case. Please reopen if bug still persist and reproducable w/ that test case. I walk the bug list currently and I cannot work with the given information. Thank you. |