vm.swap_reserved toooooo large?
kostikbel at gmail.com
Wed Dec 15 13:52:31 UTC 2010
On Wed, Dec 15, 2010 at 03:43:56PM +0200, George Mamalakis wrote:
> On 15/12/2010 13:26, Trond Endrest??l wrote:
> >On Wed, 15 Dec 2010 13:04+0200, George Mamalakis wrote:
> >>I was testing a program that would exhaust all my memory (in C++),
> >>and when this would happen, it would call set_new_handler() along
> >>with one of my functions that would inform the user about the lack
> >>of memory and then it would exit the program. Instead, the program
> >>was force-killed by the kernel (signal 9) and I was informed that:
> >If all your process' memory is exhausted, then there is no memory left
> >for the runtime system for doing I/O and the other stuff you want.
> >Next, unless I'm on drugs, maybe you should call set_new_handler()
> >before you actually run out of memory. Just my $0.02.
> >freebsd-stable at freebsd.org mailing list
> >To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> My problem was not that the program was force-killed, my problem was
> that the system reserved 500G+ of swap, even though the total size is 4G.
Read tuning(7), in particular, the description of vm.overcommit sysctl.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20101215/f6d69fbb/attachment.pgp
More information about the freebsd-stable