Bug#695757: xserver-xorg-video-radeon: Memory leak in Xorg when using oxygen-gtk as gtk2 theme
daenzer at debian.org
Tue Jan 15 00:16:15 PST 2013
On Mon, 2013-01-14 at 23:29 +0100, bluebubble wrote:
> Il 13/12/12 10:46, Michel Dänzer ha scritto:
> > If yes, you'll need to investigate the leak with valgrind or some other
> > tool for this. Note that such tools may not help on X server shutdown,
> > as the X server may still clean up the memory at that point. I think you
> > can get an intermittent leak report from valgrind by sending it some
> > signal, but I don't remember the details.
> sorry if I'm a bit late with the response.
> I've run Xorg with valgrind using this command:
> /usr/bin/valgrind -v --track-origins=yes --leak-check=full
> --show-reachable=yes --log-file=/tmp/X.log /usr/bin/Xorg $@
> Attached there is the log.
> ==27767== LEAK SUMMARY:
> ==27767== definitely lost: 88,974 bytes in 367 blocks
> ==27767== indirectly lost: 68,924 bytes in 381 blocks
> ==27767== possibly lost: 0 bytes in 0 blocks
> ==27767== still reachable: 271,956 bytes in 2,656 blocks
> ==27767== suppressed: 0 bytes in 0 blocks
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.
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
More information about the xorg-driver-ati