Summary: | SIGSEGV when disposing a dbusstring | ||
---|---|---|---|
Product: | dbus | Reporter: | Tomeu Vizoso <tomeu> |
Component: | python | Assignee: | Simon McVittie <smcv> |
Status: | RESOLVED NOTOURBUG | QA Contact: | John (J5) Palmieri <johnp> |
Severity: | normal | ||
Priority: | medium | CC: | sascha-web-bugs.freedesktop.org |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Tomeu Vizoso
2009-08-25 07:37:53 UTC
btw, this patch "fixes" the issue, so I guess we miss a GIL grab somewhere. But I really don't have much idea of this stuff. diff --git a/_dbus_bindings/abstract.c b/_dbus_bindings/abstract.c index 9a4f350..e4c4f51 100644 --- a/_dbus_bindings/abstract.c +++ b/_dbus_bindings/abstract.c @@ -440,7 +440,9 @@ DBusPythonString_tp_repr(PyObject *self) static void DBusPyStrBase_tp_dealloc(PyObject *self) { + PyGILState_STATE gil = PyGILState_Ensure(); dbus_py_variant_level_clear(self); + PyGILState_Release(gil); (PyString_Type.tp_dealloc)(self); } If the GLib bindings are unreffing Python objects (from C) without taking the GIL, I think that's NOTOURBUG. (In reply to comment #2) > If the GLib bindings are unreffing Python objects (from C) without taking the > GIL, I think that's NOTOURBUG. Closing as such. |
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.