Description of problem: My application uses QThreads as workers for network operations, python Queue for getting data for them and QSignal for sending data back to main thread. It's randomly crashing while threads are working. Version-Release number of selected component (if applicable): $ rpm -q python python-fedora python-pyside python-2.7.3-13.fc18.x86_64 python-fedora-0.3.32.3-2.fc18.noarch python-pyside-1.1.0-2.fc18.x86_64 The output is: Fatal Python error: GC object already tracked Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffa77fe700 (LWP 14466)] 0x000000361a235c55 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63 63 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); I am running it on this code: https://github.com/blaskovic/fedora-gooey-karma/tree/25b6cbfdecf1c74a63b16ef014a9aeb75a4f180a (if useful) Attaching backtraces in following comments.
Created attachment 782956 [details] backtrace
Created attachment 782957 [details] python-backtrace
I am not sure if I assigned the bug to the correct component - I cannot assume it from the backtrace.
After some research and discussions via IRC I decided to reassign it to QT. Sorry for the chaos.
I've rewrited all QSignal calls to this: http://code.activestate.com/recipes/578299-pyqt-pyside-thread-safe-global-queue-main-loop-int/ and application no longer crashes. So bug is somewhere in emitting QSignal.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.