Date: Mon, 30 Oct 2006 15:06:16 -0800 From: Jason Evans <jasone@FreeBSD.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Martin Cracauer <cracauer@cons.org>, current@freebsd.org Subject: Re: Xorg leaking memory on -current... Message-ID: <45468568.8040601@FreeBSD.org> In-Reply-To: <1582.1162249236@critter.freebsd.dk> References: <1582.1162249236@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote: > In message <20061030225118.GA10231@cons.org>, Martin Cracauer writes: >> Poul-Henning Kamp wrote on Sun, Oct 29, 2006 at 05:01:05PM +0000: >>> After a few days my Xorg will have gobbled up most of my RAM and I have >>> to restart it to get my laptop out of VAX11/750 emulation mode. >>> >>> Has anybody else noticed this ? >> I don't run an X11 on a 7-current system. My 6-stable does certainly >> not show this, the X11 server with Firefox is up for ages. >> >> It is also unusual that you actually see that much of a slowdown, >> which means it is not a plain memory leak (in which case the leaked >> pages would never be touched again, swapped out and not impact >> performance too much). >> >> Can you post the memory map? > > Nope. /proc/$pid/map is "too large" so I don't get to see it :-( There are, AFAIK, two easy ways to get around that: 1) Use the sysutils/procmap port. 2) Use dd and specify a block size that is large enough to read the whole map in one syscall. Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45468568.8040601>