Bug 281414 - Produces high CPU load when Amarok is started minimised
Summary: Produces high CPU load when Amarok is started minimised
Status: RESOLVED DUPLICATE of bug 278897
Alias: None
Product: amarok
Classification: Applications
Component: Context View/Albums (show other bugs)
Version: 2.4-GIT
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: 2.5
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-05 16:43 UTC by Frederik Schwarzer
Modified: 2011-09-05 17:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederik Schwarzer 2011-09-05 16:43:53 UTC
Version:           2.4-GIT
OS:                Linux

When I start Amarok minimised (closed it from the systray earlier), the CPU load goes to the top.

When I disable the Albums applet, things are alright.



Reproducible: Always

Steps to Reproduce:
Minimise Amarok to tray
Close Amarok by using the right-click menu
Start Amarok

Actual Results:  
It is startet to the tray (minimised) and increases system load a lot

There are some error messages in .xsession-errors WRT this problem, which are repeated a gazillion times.

=====
X Error: RenderBadPicture (invalid Picture parameter) 163
  Extension:    149 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x3c05b25
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x3c05b22
X Error: BadGC (invalid GC parameter) 13
  Major opcode: 60 (X_FreeGC)
  Resource id:  0x3c05b22
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x3c05b25
X Error: RenderBadPicture (invalid Picture parameter) 163
=====

=====
amarok(2621)/libplasma Plasma::ViewPrivate::updateSceneRect: !!!!!!!!!!!!!!!!! setting the scene rect to QRectF(0,0 2101x1.24197e+07) associated screen is -1
=====

Expected Results:  
.
Comment 1 Frederik Schwarzer 2011-09-05 17:00:34 UTC

*** This bug has been marked as a duplicate of bug 278897 ***