Crashes with GLib.child_watch_add
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pygobject (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Martin Pitt | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In a complex application, I'm seeing crashes when the destroy notify of GLib.child_
#0 0x00000000004b5c78 in tupledealloc.24592 (op=0x316dc80)
at ../Objects/
#1 0x00002b7c1553abc7 in child_watch_dnotify (data=0x345a320)
at /build/
#2 0x00002b7c1409c108 in g_source_
at /build/
#3 g_source_
at /build/
#4 0x00002b7c1409c70a in g_source_
0x3471370, context=
at /build/
#5 0x00002b7c1409eb00 in g_main_dispatch (context=0x1d08a30)
at /build/
The problem has been fixed upstream
REGRESSION POTENTIAL: Very low. This just adds locking around the reference handling to avoid race conditions with concurrent access. pyglib_
SRU TEST CASE: This is rather hard to reproduce, as it is a race condition in a multi-threaded program. As Daniel can reproduce it rather well, I suggest to ask him to verify the SRU.
See also bug 1083694 which is the same hang for software-center; this also has a test case.
Changed in pygobject (Ubuntu Quantal): | |
assignee: | nobody → Martin Pitt (pitti) |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Forgot to mention this happens with Ubuntu 12.10, both 32 and 64 bit. Package version is 3.4.0-1