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 689378 - Memory Leak
Memory Leak
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-30 21:07 UTC by Malcolm Lewis
Modified: 2017-09-04 15:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
valgrind log number one (141.60 KB, application/x-xz)
2012-11-30 21:09 UTC, Malcolm Lewis
Details
valgrind log number two (140.07 KB, application/x-xz)
2012-11-30 21:09 UTC, Malcolm Lewis
Details

Description Malcolm Lewis 2012-11-30 21:07:37 UTC
Hi
While running the gnome-shell (as an openSUSE Live CD) on my notebook I noticed the memory usage for the shell (ps aux --sort pmem) slowly rising over a number of hours. Turning on the a11y zoom feature also increased the rate of memory consumption which if left on over night would lead to a crash.

I have attached valgrind output files for both events, with inline summaries;

gnome-shell-valgrind1.log

==2906== LEAK SUMMARY:
==2906==    definitely lost: 430,360 bytes in 18,981 blocks
==2906==    indirectly lost: 64,968 bytes in 2,022 blocks
==2906==      possibly lost: 11,071,179 bytes in 65,722 blocks
==2906==    still reachable: 18,937,655 bytes in 98,809 blocks
==2906==         suppressed: 0 bytes in 0 blocks
==2906== Reachable blocks (those to which a pointer was found) are not shown.
==2906== To see them, rerun with: --leak-check=full --show-reachable=yes
==2906== 
==2906== For counts of detected and suppressed errors, rerun with: -v
==2906== ERROR SUMMARY: 72556 errors from 7260 contexts (suppressed: 95 from 3)


gnome-shell-valgrind2.log (a11y zoom on)

==4594== LEAK SUMMARY:
==4594==    definitely lost: 463,600 bytes in 20,800 blocks
==4594==    indirectly lost: 62,776 bytes in 1,953 blocks
==4594==      possibly lost: 11,547,081 bytes in 69,328 blocks
==4594==    still reachable: 18,921,722 bytes in 97,592 blocks
==4594==         suppressed: 0 bytes in 0 blocks
==4594== Reachable blocks (those to which a pointer was found) are not shown.
==4594== To see them, rerun with: --leak-check=full --show-reachable=yes
==4594== 
==4594== For counts of detected and suppressed errors, rerun with: -v
==4594== ERROR SUMMARY: 83636 errors from 7278 contexts (suppressed: 10 from 3)
Comment 1 Malcolm Lewis 2012-11-30 21:09:01 UTC
Created attachment 230342 [details]
valgrind log number one
Comment 2 Malcolm Lewis 2012-11-30 21:09:55 UTC
Created attachment 230343 [details]
valgrind log number two

a11y zoom turned on
Comment 3 Bryen Yunashko 2012-12-01 18:23:53 UTC
Also experiencing this problem when leaving Magnification on overnight.  By morning, I have to do a hard-reboot in order to get into my machine.
Comment 4 heroandtn3 2013-03-20 11:06:06 UTC
Confirm! I have had this problem when I upgrade to Ubuntu 12.10 and GNOME Shell 3.6.2. 

Everytime I click to shell calendar, memory increases about 2, 3MB.

Someone should fix this bug.
Comment 5 heroandtn3 2013-03-26 12:24:50 UTC
Here is video recording when I reproduce this bug: http://youtu.be/XnEens9Byeg
Comment 6 Florian Müllner 2013-03-26 12:30:42 UTC
(In reply to comment #4)
> Everytime I click to shell calendar, memory increases about 2, 3MB.

That is not the problem reported in this bug however, which is about memory usage when using the magnifier. What you are seeing is bug 685513, that has been fixed a while ago in the development version (and the about-to-be-released 3.8)
Comment 7 André Klapper 2017-09-04 15:29:54 UTC
As this task is nearly five years old I am closing it as obsolete. Sorry that this did not get investigated more as resources are limited.

If you still face memory leak issues in 3.24 or newer, please create new tickets. Thanks a lot for your understanding!