Why does the Xorg server reset the output when last client disconnects?
Joel Feiner
jafeiner at gmail.com
Wed May 2 12:20:27 PDT 2007
I know about Firefox and allocating pixmaps, but, as you say, they should
all go away when you close Firefox. Except that they don't. So...it's a
memory leak. Maybe it is a new bug? I don't recall it being as bad until
the last several X server versions (using git....maybe that's the problem?).
Is there any sort of data I can provide that would help diagnose this bug
for the developers?
On 5/2/07, Daniel Stone <daniel at fooishbar.org> wrote:
>
> On Wed, May 02, 2007 at 12:09:02PM -0400, Joel Feiner wrote:
> > Memory leaks are NOT a thing of the past. I have a serious one right
> now,
> > where using Firefox and visiting pages with a lot of images causes the X
> > server to leak a huge amount of heap memory, to the point that it uses
> up
> > approximately 800 MB of my 1 gig of RAM and I have to restart the X
> server
> > frequently. There are other leaks that are slower, but they're still
> > there.
>
> Unless this is some staggering new bug we've not seen before, this is
> just Firefox allocating _heaps_ of pixmaps and never bothering to free
> them (you can confirm this with xrestop). Closing Firefox undoes the
> damage.
>
> (I've had Firefox use 1.1GB of RAM and the X server use around 400MB
> before.)
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQFGOMyeRkzMgPKxYGwRAh7yAJoD7VKRAhQb6fhEf5GRpipEaiL2twCbBYWr
> 2Iy2BzOwrTbzSgbGLPz10VY=
> =KYA3
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20070502/66a6aafe/attachment.html>
More information about the xorg
mailing list