Il 15/01/13 09:16, Michel Dänzer ha scritto:
As you can see, the X server hardly leaked any memory on exit. You
really need to trigger valgrind to print information about where memory
was allocated from while memory usage appears high during runtime.
ehm I didn't find how to do that. Could you provide me some hint?
I've tested that bug outside of KDE (fluxbox and openbox to be more
specific) and with my netbook (it has an intel video card) and the bug
is there too. So this is probably not a radeon related bug (maybe it
should be moved in gtk2-engines-oxygen package?).
I've compiled the newest version of the theme engine and the bug is not
solved.
In KDE this could also be tested in system settings->application
appearance->gtk configuration->select a gtk2 theme->oxygen-gtk and then
click on the preview button and move the mouse inside the "file" menu.
Anyway any gtk2 app with a menu is enough.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org