GNOME Bugzilla – Bug 611050
Calling gobject.threads_init() causes a lot of wakeups
Last modified: 2010-04-18 16:24:09 UTC
+++ This bug was initially created as a clone of Bug #481569 +++ Hi, I'm the author of an audio player that uses PyGTK, and I have been notified that my player wakes up very frequently: https://bugs.launchpad.net/decibel-audio-player/+bug/144034 After some tests using powertop, If found that the call to gobject.threads_init() is the culprit. Even without any threads, wakeups are there just because of this call. So I'm not saying there's a bug in the way threads are managed in PyGTK, maybe these wakeups are needed, I just wanted to report that issue.
Created attachment 154669 [details] [review] proposed patch Backport from Bug 481569
Are you saying the fix in bug 481569 doesn't work or you want the patch backported to an older version of pygobject / pygtk?
(In reply to comment #2) > Are you saying the fix in bug 481569 doesn't work or you want the patch > backported to an older version of pygobject / pygtk? The fix in bug 481569 works. The patch is that bug needs to be ported to pygtk with some little pygtk modifications that I did.
I don't have commit rights, can some committer land this patch for me please?
(In reply to comment #4) > I don't have commit rights, can some committer land this patch for me please? ./gtk.override: In function ‘pygtk_main_watch_check’: ./gtk.override:1156: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result would you please check the warning and update the patch?
Created attachment 158751 [details] [review] gtk_main: fixed use of Python's SetWakeupFD API I backported the last patch from Bug 481569.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.