On Mit, 2012-12-12 at 15:48 +0100, bluebubble wrote: > Il 12/12/12 15:29, Michel Dänzer ha scritto: > > On Mit, 2012-12-12 at 13:14 +0100, bluebubble wrote: > >> Il 12/12/12 12:35, Michel Dänzer ha scritto: > >>> On Mit, 2012-12-12 at 12:22 +0100, bluebubble wrote: > >>>> > >>>> as the title state i'm noticing huge memory leaks with oxygen-gtk > >>>> theme under KDE. > >>>> With xrestop i can see with a sample application like pidgin that for > >>>> example each time i move the mouse over a popup menu resource are > >>>> never freed (pixmaps and Misc counters grows indefinitely and also > >>>> their memory occupation). > >>> > >>> Do the leaked resources persist when the application terminates? > >>> > >>> This is most likely an oxygen-gtk / GTK+ issue. > >> > >> yes sorry but i forgot to mention that very few resources are freed when > >> pidgin (or another gtk app) terminate. > >> > >> Example: > >> > >> ps aux before running pidgin: > >> [...] > > > > That may be due to heap fragmentation (memory allocated from the heap > > can only be returned to the system from the end of the allocated range, > > not in the middle of it). > > > > If the pixmaps no longer show up in xrestop, their memory is freed as > > far as the X server is concerned, and they were most certainly allocated > > by oxygen-gtk / GTK+. > > I don't think this is due to heap fragmentation I could easily made Xorg > leak hundreds of MB and they where never freed.
How is that an argument against heap fragmentation? > Pixmaps always show up in xrestop when the application is running but if > I close the application how could I know if they where actually released? As I said, if they weren't freed, they'd still show up in xrestop. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
