[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#281050: xserver-common: [i810] Memory leak



Hello,

> 1) Have you read the Debian X FAQ entry on this issue?
> 
>    .../xsf/XFree86/trunk/debian/local/FAQ.xhtml#xservmemory

I have read the entry, but I don't think I have learned anything I don't
know already.

> 2) Do you think you are experiencing the same problem as seen in bug
>    #279940?
> 
>    http://bugs.debian.org/279940

Possibly; the symptoms are similar.  However, I'm sure it's not the
flash plugin that is causing problems.  My friend also has this problem,
and he found a way to reproduce it with gpdf (Gnome's PDF viewer).  Just
use gpdf to open a largish PDF file (the IBM DB2 reference at
ftp://ftp.software.ibm.com/ps/products/db2/info/vr82/pdf/en_US/db2s1e81.pdf
having 900 pages worked well for me), and watch X memory usage soar.
Closing gpdf afterwards does not help, however, opening the same file
with gpdf again does not eat yet another 200MB of memory.  It could mean
that some buffer is allocated by X and then enlarged as needed, but not
shrunk later when it's not in use any more.

It's interesting to notice that memory is sucked further even when I'm
browsing the already opened PDF file; I just held <PageDown> for a few
moments (the page counter went up to 297), waited for gpdf to stop CPU
activity (I think it was rendering every page) and then I saw that X ate
another 30MB.  xrestop also showed a several thousand increase in the
'Extra' column.

By the way, I'm not sure, but I think my friend said that he had an ATI
video card.

I tried to reproduce this problem on several other machines (I don't
know their hardware configurations, but I'm pretty sure the software is
up to date, i.e., testing or unstable), but the problem did not manifest
itself on those machines -- gpdf happily opened the files without any
significant side effects.  I have little idea why the problem exists on
my machine and on my friend's machine, but not on the others that I have
tested.

> 3) Can you please use the "xrestop" program and provide (text)
> screenshots of its operation, so we can see if there are any
> culpable clients?

I am attaching snapshots of top, pmap and xrestop before starting gpdf
(suffix ".before"), after opening the DB2 reference with gpdf (suffix
".after", and after closing gpdf (suffix ".closed").  My XF86Config-4
and output of xdpyinfo are included as well.

Note that I wasn't using gpdf previously (nor was I opening large PDFs),
so I don't think you should put all the blame on it as you did for the
flash plugin.  I am experiencing a gradual increase of memory usage
rather than sudden jumps.  There might be a bug in gpdf, but I am
concerned with the fact that the memory is not released even after I
quit gpdf.

I now tried opening several large apps (OpenOffice.org, GIMP, Eclipse,
etc.) and some of the hogged-up memory was swapped out (resident block
of X fell from 230MB to 107MB).  At least that stuff swaps out, but it
still makes my system rather slow (perhaps because it starves the
filesystem cache).

Another very thing I have experienced a few times is an almost-complete
freeze of my machine when exiting a heavy app (I remember experiencing
it with Eclipse and some other programs too).  Even the mouse cursor
stops moving, and for about one minute there is very intensive hard disk
activity.  Then the system starts responding again as if nothing had
happened.  I could not find anything interesting in the logs or output
of `top`.  This might not be related to this bug, but I'm including it
in case other people have experienced such a thing too.

My machine is a Toshiba laptop with a 2.2GHz P4 and 512MB of RAM, Intel
855GM video chipset, I'm using Debian unstable.

I hope I provided some useful information (I will be happy to provide
more if you need anything else).  It's a pity that I don't really have
time right now (well, to be honest, not quite enough experience
either...) to fire up a debugger and chase the culprit myself.

-- 
Gintautas Miliauskas <gintas@akl.lt>

Attachment: x-leak-info.tar.gz
Description: application/compressed-tar

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?=


Reply to: