I see this problem too. The amount of CPU time wasted seems to be
proportional to the length of the package's changelog. A kernel package
with very long changelog causes update-manager to hang using 100% CPU
for a long time, whereas it only hangs very briefly if you click a
package whose changelog is smaller.

This happens even if the user did not click "Technical description" so
the changelog is not shown on-screen.

It's really annoying. Even if you're just un-checking boxes to deselect
packages, you get the 100% CPU hang. (Try moving down the list un-
checking several boxes quickly.)

To reproduce should be fairly easy:
- Run "top" (or some other load monitor) in a terminal.
- Run update-manager and wait until the list of available updates appears.
- Click the top item, then keep tapping cursor-down to move to the next one.
- If you hit an update with a long changelog (e.g. kernel package), notice that 
CPU usage goes to 100% for a long time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1183672

Title:
  update-manager grabs major share of CPU&RAM when browsing list items

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1183672/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to