Open GoogleCodeExporter opened 8 years ago
Same here. How can I help? Life sucks without globalmenu.
--Gene
Original comment by selko...@gmail.com
on 11 Mar 2010 at 1:55
first kill GlobalMenu.PanelApplet, ignore the gnome error dialog,
start the applet with valgrind:
valgrind --leak-check=full GlobalMenu.PanelApplet --log-file=vallog
count seconds till 10 so that the applet is fully loaded
back to the error dialog and click reload.
Now use the applet(it will become ridiculously slow until the memory leak
becomes
noticeable.
break valgrind and post vallog here. Or study the log, fix the leak and post a
patch here.
I'll be more than happy to merge it to the git.
Original comment by rainwood...@gmail.com
on 11 Mar 2010 at 2:13
I'm using gnome-applet-globalmenu 0.7.9-0ubuntu1~ppa1~lucid2 from the
globalmenu-team PPA on Lucid 64bit (2x AMD Opteron Dual-Core = 4 cores).
Here at work I have the memory leak problem. After about 2 hours working in
various programs, the GlobalMenu process consumes hundreds of MB RAM and if I
don't kill/reload it, it will become slower and slower until even X freezes
while waiting for GlobalMenu to switch the menu. It seems like it grows ~1MB
when switching from one program to another.
At home, I don't have these problems (mostly same software-configuration on an
Intel Core 2 Quad).
I attached the vallog as you requested.
Original comment by mbi...@gmail.com
on 19 Jul 2010 at 12:46
Attachments:
Same problem here. It may use 700 Mo...
I have Ubuntu 10.04 64bit
Original comment by math...@gmail.com
on 20 Jul 2010 at 9:56
same problem here. Memory usage keeps increasing till memory is exhausted.
ubuntu 10.04 32 bit , 1 gb Ram.
Original comment by jfr...@in.com
on 25 Aug 2010 at 4:14
Could you people check whether you have the package appmenu-gtk installed? From
reading at
http://www.webupd8.org/2010/07/nautilus-memory-leak-fix-ubuntu-1004.html this
might be the source of the problem. I just uninstalled it here and now
GlobalMenu doesn't slow down anymore...
Original comment by mbi...@gmail.com
on 9 Sep 2010 at 9:07
Original issue reported on code.google.com by
58desi...@gmail.com
on 4 Jan 2010 at 3:57Attachments: