I typically leave gnome-panel (gnome 2.20.1 on Solaris Nevada) running for weeks in a Sun Ray session. The heap does appear to be growing over time:
pmap -x of gnome-panel process BEFORE restart of gnome-panel: 22817: gnome-panel --sm-client-id 11819cdc28000119515176100000052150048 --scr Address Kbytes RSS Anon Locked Mode Mapped File 00010000 496 488 - - r-x-- gnome-panel 0009A000 24 24 16 - rwx-- gnome-panel 000A0000 3456 3456 1432 - rwx-- [ heap ] 00400000 12288 12288 12288 - rwx-- [ heap ] F9280000 1312 1024 - - r-x-- libcrypto.so.0.9.8 F93D8000 104 96 - - rwx-- libcrypto.so.0.9.8 F93F2000 8 - - - rwx-- libcrypto.so.0.9.8 F9400000 5344 1640 - - r---- icon-theme.cache ... pmap -x of gnome-panel process AFTER restart of gnome-panel: 3024: gnome-panel --sm-client-id 11819cdc28000119515176100000052150048 --scr Address Kbytes RSS Anon Locked Mode Mapped File 00010000 496 488 - - r-x-- gnome-panel 0009A000 24 24 24 - rwx-- gnome-panel 000A0000 1960 1960 1960 - rwx-- [ heap ] F9400000 5344 1640 - - r---- icon-theme.cache F9C00000 7056 5904 - - r---- icon-theme.cache FA350000 16 16 - - r-x-- libmoniker_std_2.so FA362000 8 8 8 - rwx-- libmoniker_std_2.so FA370000 32 32 - - r-x-- libstartup-notification-1.so.0.0.0 FA386000 8 8 8 - rwx-- libstartup-notification-1.so.0.0.0 FA390000 8 8 8 - rwx-- [ anon ] FA3A0000 88 80 - - r-x-- libgnome-desktop-2.so.2.3.14 FA3C4000 8 8 8 - rwx-- libgnome-desktop-2.so.2.3.14 FA3D0000 16 16 - - r-x-- libpixbufloader-png.so FA3E2000 8 8 8 - rwx-- libpixbufloader-png.so FA3F0000 64 16 16 - rwx-- [ anon ] FA410000 384 192 - - rwxs- [ shmid=null ] FA480000 3520 1496 - - r---- icon-theme.cache FA810000 32 32 - - r-x-- libesd.so.0.2.38 ... I'll spare the details of the Anonymous memory used by all libraries in gnome-panel's address space, but notice that restarting gnome-panel reduced the heap from over 15M to about 2M when I restarted gnome-panel. Occasionally I see halting behaviour in gnome-panel menus which may be caused by paging activity. Did anything recently change in gnome-panel's memory management? When was gslice introduced? How can I disable it? Gslice might not be necessary on Solaris since running with a slab allocator is as simple as setting LD_PRELOAD to libumem.so. Ross Burton wrote: > On Fri, 2007-11-30 at 10:51 +0100, Mark wrote: > >>> It's only leaked 2000 bytes, you'll need to do more research on the >>> 422000 bytes which are still reachable. >>> >> how do i do that? (gonna read the "MemoryReduction" docs soon) >> > > Read the valgrind help page. > > Ross > > ------------------------------------------------------------------------ > > _______________________________________________ > desktop-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
