After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603580 - Shell performance gets slower as time passes
Shell performance gets slower as time passes
Status: RESOLVED DUPLICATE of bug 642652
Product: gnome-shell
Classification: Core
Component: drivers
unspecified
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2009-12-02 11:50 UTC by emigrant
Modified: 2011-06-15 22:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description emigrant 2009-12-02 11:50:13 UTC
At the beginning of the session the performance is good.
but as time passes, the performance gets slower and when i click activities the zoom in/ zoom out process is not well. also scrolling down the application menu makes the arrow of the scroll bar disapper.

system info:
core2dua E8400@3Ghz
2GB ram
01:00.0 VGA compatible controller: ATI Technologies Inc RV505 CE [Radeon X1550 64-bit]
Comment 1 Giovanni Campagna 2010-06-25 16:56:37 UTC
I can confirm this behaviour, even though I have a different graphic card.
Upon loading, Shell is fast and clean, progressively it becomes slower, in particular in the message tray area, where the animation is reduced to one or two steps.

I have an Intel GMA 4500HD, on a Dell Latitude system (Core 2 Duo P9700 @2.80GHz, 4 GB RAM)
Video drivers are 2.11.0, xorg-xserver 1.8.0, libdrm 2.4.20, mesa 7.8.1, linux 2.6.33.5, cairo 1.8.10, (glitz 0.5.6, though I'm not sure this is relevant), clutter is clutter-1.2/HEAD, mutter and shell are git master
Comment 2 Jean-François Fortin Tam 2011-06-15 22:44:24 UTC
Thanks for taking the time to report this bug.
Could you try this with recent versions?

Anyway, if that's still the case, this seems like a duplicate of bug #642652 or bug #649477.

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