Bug 640972
| Summary: | [abrt] sugar-0.90.2-1.fc14: Process /usr/bin/python was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernie Innocenti <bernie+fedora> | ||||
| Component: | python | Assignee: | Dave Malcolm <dmalcolm> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | bernie+fedora, dmalcolm, ivazqueznet, james.antill, johnp, jonathansteffan, pbrobinson, sebastian, simon, smparrish, tomeu | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:fdb01b414ad94f4ae0cc63247140da39f46f09f8 | ||||||
| Fixed In Version: | pygobject2-2.21.5-4.fc14 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-10 13:30:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Bernie Innocenti
2010-10-07 12:16:10 UTC
Created attachment 452094 [details]
File: backtrace
(In reply to comment #0) > 1. click on an icon (in this case, it was the Log activity) You mean it happens with other activities as well? (Make sure you haven't started Log when you try) (In reply to comment #2) > You mean it happens with other activities as well? (Make sure you haven't > started Log when you try) Yes, this is for sure sl#2064: it happens by clicking on random icons in the journal or in the activity list... even on the frame. We've been chasing it for 6 months. (In reply to comment #3) > (In reply to comment #2) > > You mean it happens with other activities as well? (Make sure you haven't > > started Log when you try) > > Yes, this is for sure sl#2064: it happens by clicking on random icons in the > journal or in the activity list... even on the frame. We've been chasing it for > 6 months. So the reason why I'm asking this is because earlier it was suggested that it happened only after a DBus exception, and Log in F14 is known to raise one because it expects the old PS being there. So if anybody has a hint of what can be leaving the refcount wrong, it would help a lot tracking this bug. The inconsistency in the reference counts during garbage collection could be caused by memory corruption or a bug in one of the Python bindings: dbus-python, pygtk2, pygobject2, gnome-python2-rsvg... It may also be a threading bug in the gtk bindings, because the dbus bindings spawn an extra thread which re-enters the gtk mainloop. Reassigning to Python for the time being. Malcolm, please help: this bug is extremely hard to reproduce and extremely annoying for our users. (In reply to comment #4) > So the reason why I'm asking this is because earlier it was suggested that it > happened only after a DBus exception, and Log in F14 is known to raise one > because it expects the old PS being there. In this particular case, Sugar died taking the X session with it, before Log could initialize. In the log of the Sugar process, there's one dbus exception fired at initialization time: 1286452807.152217 ERROR dbus.proxies: Introspect error on org.freedesktop.ohm:/org/freedesktop/ohm/Keystore: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ohm was not provided by any .service files 1286452807.153741 ERROR root: Cannot unfreeze the DCON :30 At least 10 seconds elapsed between this and the actual death, but it's possible that Python's GC had not ever fired before. Here's a working theory: clicking on icons causes the activity launcher to start, which often allocates enough memory to trigger a collection round. This would explain why we usually get the crash just after clicking on icons. gc->gc.gc_refs really is 0:
(gdb) p generations[0].head
$8 = {gc = {gc_next = 0x1e336f0, gc_prev = 0x1c66770, gc_refs = 0}, dummy = <invalid float value>}
Full coredump available here: http://people.sugarlabs.org/bernie/sugar/sl2064-coredump
Resume it with:
gdb /usr/bin/python sl2064-coredump
You need python-2.7-8.fc14.1.x86_64 to use the above coredump. I could provide the binary if needed. pygobject2-2.21.5-4.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/pygobject2-2.21.5-4.fc14 pygobject2-2.28.4-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/pygobject2-2.28.4-3.fc15 Package pygobject2-2.21.5-4.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pygobject2-2.21.5-4.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/pygobject2-2.21.5-4.fc14 then log in and leave karma (feedback). pygobject2-2.28.4-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. pygobject2-2.21.5-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |