Bug 14134

Summary: Crash when context is shared among 2 processes.
Product: Mesa Reporter: Johan Bilien <jobi>
Component: GLXAssignee: mesa-dev
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Johan Bilien 2008-01-19 09:51:10 UTC
I am seeing the following crash when sharing a context between 2 processes with glXImportContext (with LIBGL_ALWAYS_INDIRECT set):


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7c6c6b0 (LWP 3639)]
0xb7b9a434 in GetDrawableOrPixmap (glxc=0x0, drawId=77594626, 
    ppGlxDraw=0xbfeaaa48, ppPixmap=0xbfeaaa44, client=0x8e94a58)
    at ../../../GL/glx/glxcmds.c:475
475     ../../../GL/glx/glxcmds.c: No such file or directory.
        in ../../../GL/glx/glxcmds.c
(gdb) bt
#0  0xb7b9a434 in GetDrawableOrPixmap (glxc=0x0, drawId=77594626, 
    ppGlxDraw=0xbfeaaa48, ppPixmap=0xbfeaaa44, client=0x8e94a58)
    at ../../../GL/glx/glxcmds.c:475
#1  0xb7b9a73c in __glXDisp_SwapBuffers (cl=0x8e30768, 
    pc=0x9209638 "\237\v\003") at ../../../GL/glx/glxcmds.c:1502
#2  0xb7b9e006 in __glXDispatch (client=0x8e94a58)
    at ../../../GL/glx/glxext.c:561
#3  0x0814d82e in XaceCatchExtProc (client=0x8e94a58) at ../../Xext/xace.c:299
#4  0x0808d1ef in Dispatch () at ../../dix/dispatch.c:502
#5  0x0807470b in main (argc=9, argv=0xbfeab004, envp=Cannot access memory at address 0x8
) at ../../dix/main.c:452


I have Xserver 1.4.1~git20080118 (debian unstable), mesa 7.0.2, video-intel 2.2.0 (intel 945 chipset)
Comment 1 GitLab Migration User 2019-09-18 17:11:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/53.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.