Bug 12431 - Savage: f-spot crashes on glXDestroyContext
Summary: Savage: f-spot crashes on glXDestroyContext
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-14 16:38 UTC by Frank de Lange
Modified: 2019-10-14 13:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Frank de Lange 2007-09-14 16:38:14 UTC
There are several reports out on crashes with f-spot (gnome photo mgmt app, written in mono) which seem to have in common that the crashes occur on machines using the savage drm module and dri driver. I reported a workaround to these problems on the Gnome bugzilla:

http://bugzilla.gnome.org/show_bug.cgi?id=458688

(There is a stack trace in the gnome bug report)

This keeps the program from crashing but it does not solve the real problem. I suspect that the real bug hides somewhere in either the savage_dri driver or the savage drm module. As to what is happening here I'm as of yet in the dark. Possibly related to the use of more than one OpenGL context?

As stated in the Gnome bug report I tried several workarounds to get rid of the crashes. Explicit calls to glXMakeCurrent, glFinish, glFlush, glXWaitX and
glXWaitGL before the call to glXDestroyContext did not help. 

Should this bug be reported to Mesa instead of DRI?
Comment 1 Martin Peres 2019-10-14 13:20:09 UTC
Hi,

Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org.

To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default).

Sorry about the noise!


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.