freebsd stable - Aug 2003 - swap_pager: out of swap space

Aug 11 03:56:34 danux /kernel: swap_pager: out of swap space
Aug 11 04:02:34 danux /kernel: swap_pager_getswapspace: failed
Aug 11 04:02:34 danux /kernel: pid 278 (XFree86), uid 0, was killed: out
of swap space

i was actually looking at the screen and then everything stopped (mouse
etc). i could not switch to console, but a ctrl+alt+del rebooted fine.

one thing that could be taking a lot of memory was a program called
"xwatch" (/usr/ports/sysutils/xwatch) reading a log file (with a lot
of
activity from a software i'm developing) and xwatch might not be
limiting its buffer... ? i don't know, wouldnt the kernel kill xwatch
instead of xfree86?

i appreciate any info on this. thanks.

FreeBSD danux.slashlog.org 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Aug  5
03:48:15 EDT 2003 daniel@danux.slashlog.org:/usr/obj/usr/src/sys/DANUX 
i386

-- 
daniel

On Mon, 2003-08-11 at 01:21, Daniel C Bastos wrote:
> Aug 11 03:56:34 danux /kernel: swap_pager: out of swap space
> Aug 11 04:02:34 danux /kernel: swap_pager_getswapspace: failed
> Aug 11 04:02:34 danux /kernel: pid 278 (XFree86), uid 0, was killed: out
> of swap space
> 
> i was actually looking at the screen and then everything stopped (mouse
> etc). i could not switch to console, but a ctrl+alt+del rebooted fine.
> 
> one thing that could be taking a lot of memory was a program called
> "xwatch" (/usr/ports/sysutils/xwatch) reading a log file (with a
lot of
> activity from a software i'm developing) and xwatch might not be
> limiting its buffer... ? i don't know, wouldnt the kernel kill xwatch
> instead of xfree86?
> 
> i appreciate any info on this. thanks.
Pixmaps allocated by X clients are actually allocated by the server.  If
xwatch leaked that memory, or just allocated enough of it, it could
cause XFree86 to be chosen by the OOM killer.

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org