Quoting Giovanni <[EMAIL PROTECTED]>:
> If I don't connect the webcam, the Fox is becoming very slow after
> some hours from the last reboot. It seems like there is some process
> which has memory leakage and is filling up the Fox memory.
Linux has an overly optimistic way of allocating memory - here's the relevant
passage from 'man malloc':
BUGS
By default, Linux follows an optimistic memory allocation strategy.
This means that when malloc() returns non-NULL there is no guarantee
that the memory really is available. This is a really bad bug. In case
it turns out that the system is out of memory, one or more processes
will be killed by the infamous OOM killer. In case Linux is employed
under circumstances where it would be less desirable to suddenly lose
some randomly picked processes, and moreover the kernel
version is suf‐
ficiently recent, one can switch off this overcommitting behavior using
a command like
# echo 2 > /proc/sys/vm/overcommit_memory
See also the kernel Documentation directory, files vm/overcommit-
accounting and sysctl/vm.txt.
- Try disabling overcommit as a first option; if the program that leaks is
reasonably behaved, you should at least be able to spot it.
- A reasonable bet would be that the program is indeed foxserve, though - have
you tried noting down its memory size at start and after a few hours?
Ant9000
