Created attachment 31577 [details] manywin.log O.S. - Ubuntu-9.10-32bit ASIC- RV516 Details of the X-stack: ---------------------- drm : 2.4.5 mesa/mesa : 7.7 xorg/xserver : 1.6.0 xorg/xf86-video-ati: 20th November-2009 O.S.- Ubuntu-9.04-64 ASIC-RV516 Steps to Reproduce: ====================== run mesa/progs/xdemos ./mayawin 10 Observed Behaviour : ===================== Segmentation fault observed.(log attached)
Created attachment 31578 [details] xorg.conf
Created attachment 31579 [details] lspci
Created attachment 31580 [details] glxinfo
Created attachment 31581 [details] Xorg.log
Is this still an issue with newer versions of mesa? Any chance you could get a backtrace with gdb?
This happens only in DRI1 because bo manager in mesa frees all buffers ever allocated for context in context destruction. Result is that shared objects are destroyed even tough there is still references to them in other active contexts.
(In reply to comment #5) > Is this still an issue with newer versions of mesa? Any chance you could get a > backtrace with gdb? > The issue is fixed in the latest build with Mesa version 7.8-devel
It's still happening here, with git master. Maybe related: bug #22868. Card: GL_RENDERER = Mesa DRI R300 (RV530 71C5) 20090101 x86/MMX/SSE2 TCL
This report should either be reassigned to r300g if it still happens with that, or resolved as WONTFIX, as r300c is dead.
The classic r300 driver has been abandoned long ago. It was replaced by the Gallium driver r300g. If you have issues with r300g please file a new bug report with component Drivers/Gallium/r300 Thanks.
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.