On 5 December 2013 18:18, Jasper St. Pierre <jstpie...@mecheye.net> wrote: > > If you can try running gnome-shell with valgrind or massif, that will give > you more accurate allocation counts, since it will count all the times that > some code runs malloc(). The profiling results from massif would be useful > regardless, but I think you'll find that we only allocate around 300M or so.
If you just want to know how much memory is being allocated with malloc and have some insights of what is going on in the heap, mallinfo(3) is a simpler way to find that out. Regards, Tomeu > On Thu, Dec 5, 2013 at 7:54 AM, Petko Ditchev <pditc...@gmail.com> wrote: >> >> Yes , I guess it's related . I dismissed that bug for being too old to be >> related , but the comments are recent and similar to what I have . Thanks >> for the pointer. >> >> >> On 12/05/2013 02:50 PM, Germán Póo-Caamaño wrote: >>> >>> On Thu, 2013-12-05 at 14:32 +0200, Petko Ditchev wrote: >>>> >>>> I see that the process starts eating memory in no particular way . >>>> Sometimes it stays at ~120MB , and some times it starts rising and can >>>> reach 1.5GB . I alt+F2 : 'r' , to restart the shell and put out the fire >>>> , but the issue has to get fixed at some point , and I don't know what >>>> additional info I can give in a bug report . I'm on Manjaro , updated >>>> (gnome-shell 3.10.2.1-1) . >>> >>> Maybe related to https://bugzilla.gnome.org/show_bug.cgi?id=685513 >>> >> >> _______________________________________________ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/desktop-devel-list > > > > > -- > Jasper > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
