Hello, > Anyway, one way to test at least parts of my hypothesis would be simply to > turn off the XAA pixmap cache. To do this, add the following line to the > "Device" section of your XF86Config-4 file: > > Option "XaaNoPixmapCache" > > It might be worth trying the following as well: > > Option "XaaNoOffscreenPixmaps" > > Both of the above are documented in XF86Config-4(5x), by the way. I added both of these to the "Device" section, didn't change anything. I also tried to add them to the "Screen" section (as the manual says), without any difference either. Taking this a step further, I completely disabled XAA (Option "Accel" "off"). It did wonders to slowing my system to a crawl, yet gpdf would still hoard memory, which means that the problem has not gone away. I presume that these results do not go well with your hypothesis? Is there anything else I can do to at least help find out which part of X is the culprit? This bug is really a PITA for me (I even made a tiny cron script that mails me if X takes up more than 80MB (resident); it takes about two days to reach that threshold). Thanks for your help, -- Gintautas Miliauskas <gintas@akl.lt>
Attachment:
signature.asc
Description: =?iso-8859-2?Q?=A9i?= =?iso-8859-2?Q?_lai=B9ko?= dalis yra =?iso-8859-2?Q?pasira=B9yta?= skaitmeniniu =?iso-8859-4?Q?b=FEdu?=