Posted by StrangelyTyped on Sep 20, 2021; 8:40pm
URL: https://forum.jogamp.org/Model-corruption-with-Background-Node-tp4041238p4041297.html

Thanks for looking into it, no worries about being busy I just wanted to make sure it didn't get lost. I'll keep an eye out for new releases.

Interestingly, re-setting the offscreen buffer in j3d 1.6.2/jogl 2.4.0 causes a segfault in the VM I'm primarily trying to develop in (hence the vmwgfx_dri.so)

Current thread (0x00007f806000c040):  JavaThread "J3D-Renderer-1" [_thread_in_native, id=45673, stack(0x00007f80ac15f000,0x00007f80ac260000)]

Stack: [0x00007f80ac15f000,0x00007f80ac260000],  sp=0x00007f80ac25d748,  free space=1017k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [vmwgfx_dri.so+0x1377b6]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  jogamp.opengl.x11.glx.GLXExtImpl.dispatch_glXCreateContextAttribsARB0(JJJZLjava/lang/Object;IJ)J+0
j  jogamp.opengl.x11.glx.GLXExtImpl.glXCreateContextAttribsARB(JJJZLjava/nio/IntBuffer;)J+75
j  jogamp.opengl.x11.glx.X11GLXContext.createContextARBImpl(JZIII)J+521
j  jogamp.opengl.GLContextImpl.createContextARB(JZ)J+333
j  jogamp.opengl.x11.glx.X11GLXContext.createImpl(J)Z+685
j  jogamp.opengl.GLContextImpl.makeCurrentWithinLock(I)I+224
j  jogamp.opengl.GLContextImpl.makeCurrent(Z)I+488
j  jogamp.opengl.GLContextImpl.makeCurrent()I+2
j  javax.media.j3d.JoglPipeline.createNewContext(Ljavax/media/j3d/Canvas3D;Ljavax/media/j3d/Drawable;Ljavax/media/j3d/Context;ZZ)Ljavax/media/j3d/Context;+167
j  javax.media.j3d.Canvas3D.createNewContext(Ljavax/media/j3d/Drawable;Ljavax/media/j3d/Context;ZZ)Ljavax/media/j3d/Context;+9
j  javax.media.j3d.Canvas3D.createNewContext(Ljavax/media/j3d/Context;Z)Ljavax/media/j3d/Context;+11
J 1190 c1 javax.media.j3d.Renderer.doWork(J)V (6213 bytes) @ 0x00007f80e8255ff4 [0x00007f80e824adc0+0x000000000000b234]
j  javax.media.j3d.J3dThread.run()V+19
v  ~StubRoutines::call_stub

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x00000000000032fc

This is specifically in response to the new line you suggested adding, and the first render actually goes through just fine. I assume it's specific to this particular environment though given the .so mentioned and since you were able to work around the issue yourself.