#30: Insane RAM usage
-----------------------------------------------+----------------------------
Reporter: Gilou <[EMAIL PROTECTED]> | Owner: admin
Type: Bugs | Status: new
Priority: 1 | Milestone:
Component: Liquidsoap | Version: 0.3.3
Resolution: | Keywords: RAM leak 64bits
-----------------------------------------------+----------------------------
Comment (by toots):
An interesting documentation for working around the bug:
Since 2.1.27 there are a sysctl VM_OVERCOMMIT_MEMORY and proc file
/proc/sys/vm/overcommit_memory with values 1: do overcommit, and 0
(default): don't. Unfortunately, this does not allow you to tell the
kernel to be more careful, it only allows you to tell the kernel to be
less careful. With overcommit_memory set to 1 every malloc() will succeed.
When set to 0 the old heuristics are used, the kernel still overcommits.
Since 2.5.30 the values are: 0 (default): as before: guess about how much
overcommitment is reasonable, 1: never refuse any malloc(), 2: be precise
about the overcommit - never commit a virtual address space larger than
swap space plus a fraction overcommit_ratio of the physical memory. Here
/proc/sys/vm/overcommit_ratio (by default 50) is another user-settable
parameter. It is possible to set overcommit_ratio to values larger than
100. (See also Documentation/vm/overcommit-accounting.)
[http://www.win.tue.nl/~aeb/linux/lk/lk-9.html]
--
Ticket URL: <http://savonet.rastageeks.org/ticket/30#comment:7>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
