gnomad2 uses 100% cpu
Bug #360442 reported by
chrisV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOMAD |
Unknown
|
Unknown
|
|||
gnomad2 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnomad2
On Intrepid, gnomad2 uses 100% cpu after it has been started on my x86 machine - not viciously so, as it is not a tight loop, but is a callback loop in GMainLoop. However, it can easily be observed by starting gnomad2 and then running top, and is prejudicial to my laptop battery life.
This is caused by calling g_idle_add() in src/filelist.c and src/jukebox.c being passed a callback (gtk_widget_
A patch which deals with this is attached.
Related branches
To post a comment you must log in.
I was unable to recreate this on Jaunty Jackalope using gnomad2 version 2.9.1-1.1ubuntu1 on an amd64 machine. Do you happen to have an mtp device connected when you find this bug? Thanks in advance.