Bug 11506 - Crash in libGLcore.so (XMesaResizeBuffers) on exit from Danger from the Deep
Summary: Crash in libGLcore.so (XMesaResizeBuffers) on exit from Danger from the Deep
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/GLX (show other bugs)
Version: 7.2 (2007.02)
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Depends on:
Blocks: xorg-7.5
  Show dependency treegraph
Reported: 2007-07-09 04:02 UTC by Jure Repinc
Modified: 2009-08-31 17:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Jure Repinc 2007-07-09 04:02:19 UTC
I have Xorg server 1.3.0, Mesa 6.5.3, open source ATI driver (from Git, synced on 2007-07-08).

To reproduce:
1. open Danger from the Deep 0.3.0 so that it shows the main menu
2. exit from the game
3. X crashes

0: /usr/bin/X(xf86SigHandler+0x81) [0x80cd181]
1: [0xb7f22420]
2: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaResizeBuffers+0x2a) [0xaf97e63a]
3: /usr/lib/xorg/modules/extensions//libGLcore.so [0xaf97b1e0]
4: /usr/lib/xorg/modules/extensions//libglx.so [0xb7be48ea]
5: /usr/bin/X(ReparentWindow+0x1a1) [0x80763e1]
6: /usr/bin/X(ProcReparentWindow+0xd5) [0x8087b55]
7: /usr/bin/X [0x8149341]
8: /usr/bin/X(Dispatch+0x19d) [0x808812d]
9: /usr/bin/X(main+0x48e) [0x807028e]
10: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7d2f83c]
11: /usr/bin/X(FontFileCompleteXLFD+0xa1) [0x806f5b1]

Fatal server error:
Caught signal 11.  Server aborting
Comment 1 Michel Dänzer 2007-07-09 04:09:57 UTC
Could be covered by bug 7205. Also, may I ask why you're not using direct rendering?
Comment 2 Jure Repinc 2007-07-09 04:40:47 UTC
Well I have this ATI Radeon Xpress 200m integrated in laptop and there is no support for direct rendering in open source drivers yet.
Comment 3 Daniel Stone 2009-08-31 17:57:52 UTC
i suspect this is fixed now, but if not, please reopen.

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.