Re: xorg 6.9.0 mem leak
- From: Randy Bush <randy@xxxxxxx>
- Date: Mon, 30 Jan 2006 13:49:43 -0800
> Sorry, what are you saying the problem is here?
maybe this will appeal more
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
2166 randy 4 20 0 166M 108M kserel 3:51 0.00% firefox-bin
1343 randy 1 96 0 126M 83500K select 2:44 2.00% Xorg
1394 randy 4 20 0 102M 51456K kserel 0:08 0.00% nautilus
and the Xorg one just keeps growing and growing and growing.
i am also suspicious of firefox, which grows as well.
nautilus is a pig, bit stays the same size.
it's the xorg which will eventually cause swap and then, as it
fills swap, death.
randy
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: xorg 6.9.0 mem leak
- From: Matthew D. Fuller
- Re: xorg 6.9.0 mem leak
- From: Kris Kennaway
- Re: xorg 6.9.0 mem leak
- References:
- xorg 6.9.0 mem leak
- From: Randy Bush
- Re: xorg 6.9.0 mem leak
- From: Ricardo A. Reis
- Re: xorg 6.9.0 mem leak
- From: Randy Bush
- Re: xorg 6.9.0 mem leak
- From: Randy Bush
- Re: xorg 6.9.0 mem leak
- From: Jiawei Ye
- Re: xorg 6.9.0 mem leak
- From: Kris Kennaway
- xorg 6.9.0 mem leak
- Prev by Date: Re: panic: vm_page_free_toq: freeing mapped page
- Next by Date: Re: xorg 6.9.0 mem leak
- Previous by thread: Re: xorg 6.9.0 mem leak
- Next by thread: Re: xorg 6.9.0 mem leak
- Index(es):