On Thu, Jan 20, 2005 at 01:00:02PM +0200, Modestas Vainius wrote: > After a few hours of investigation I've tracked down this bug. At > least I've discovered what code causes Xserver to leak memory, when > the bug is "exploited" by gpdf. It's as simple as the following: Nice work. It explains why I discovered the problem so often by running Firefox, since Firefox will change to the (animated) wait-cursor lots of times. > I've made a simple gtk program, which starts executing the code above > infinite number times once you press the "Test memleak!" button (thus > you will need to use CTRL+C or `kill` to terminate the program). Here > it's the step-by-step guide to reproduce the memleak: Yup, running for 30 seconds its enough to bring my system to swapping, and pmap shows: [root@kobayashi-maru ~]# pmap -x $(pidof X) [...] 0a512000 360896 - - - rw--- [ anon ] [...] With that I guess that bugs should be fixed soon, thanks again. Regards, Matthias
Attachment:
pgp3DTtpLrv56.pgp
Description: PGP signature