Version: 6.3 Severity: normal Reportbug eats about 30% of cpu doing essentially nothing. I guess code which does progress bar updating is called too often and overhead is just so big. Reportbug can be in such state for few minutes, if for example smtp connection is very slow.
Hi, this was reported against the old gtk2 interface (python-gtk2), which no longer exists: the GTK UI now uses GTK3 through GObject introspection. A GTK3 progress bar pulsed the way the current UI does it (every 10 ms) used about 6% CPU in a test under Xvfb, not 30%. Closing; if you still see a high load with a current version, please reopen with the details. Regards, Sandro