0 Replies Latest reply on Mar 26, 2012 2:41 AM by dhdd

    Crash in ukiCreateContext

    dhdd

      Hi.

       

      I am running an

      • OpenGL app (using LWJGL)
      • under 32bit Linux
      • with an embedded ATI MXM module E4690 with 11.12 drivers

       

      After running for hours and sometimes days the application segmentation faults in the driver method ukiCreateContext. The stack below that call is different at times, but it mostly happens when I blit an FBO after rendering to a texture, multisampled. The fact that I cannot debug, etc. into the driver and the fact that I cannot find anything on the net about this makes it hard to fix.

       

      Java SEGV message:

      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      #  SIGSEGV (0xb) at pc=0x00007fcd328dfaa1, pid=8478, tid=140519401658112
      #
      # JRE version: 6.0_26-b03
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
      # Problematic frame:
      # C  [fglrx_dri.so+0xaa7aa1]  ukiCreateContext+0xaa7aa1
      #
      # 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.
      #
      
      

       

      The top of the stack:

      Stack: [0x00007fcd38f51000,0x00007fcd39052000],  sp=0x00007fcd3904feb0,  free space=1019k
      Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
      C  [fglrx_dri.so+0xaa7aa1]  ukiCreateContext+0xaa7aa1
      
      
      [error occurred during error reporting (printing native stack), id 0xb]
      
      
      Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
      j  org.lwjgl.opengl.EXTFramebufferBlit.nglBlitFramebufferEXT(IIIIIIIIIIJ)V+0
      j  org.lwjgl.opengl.EXTFramebufferBlit.glBlitFramebufferEXT(IIIIIIIIII)V+35
      
      

       

      What does that ukiCreateContext method do and does anyone have an idea what I may be doing wrong to cause this? Is it a known driver-bug? How shall we proceed?

       

      Thanks for your help,

      dhdd