Comment 6 for bug 49901
Revision history for this message
| David Taylor (me-davidandrewtaylor) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I get this problem as well with Amarok 1.4.3 (Brandon's build) (only less pronounced - 6/7 seconds to respond or so), I just never realised that Amarok was causing the problem but closing it does make Katapult respond really sharply. I don't think that it is anything to do with resources as:
without Amarok open I'm running at 10% and memory at 53% usage
with Amarok open, I'm at 15% and memory at 59% usage
and I can replicate the fault with the resources like that...
That's a little excessive for an idle Jukebox but I wouldn't think it would cause Katapult to become this laggy as everything else still runs AOK.