On Don, 2013-01-17 at 09:13 +0100, bluebubble wrote: > 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?
As I said, I'd have to research it myself. I vaguely remember one can send some signal to the valgrind process to trigger it. > 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?). The evidence does seem to point in that direction. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
