id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	appname	phpversion	exts	sapi	probability	blockedby	blocking
258	reproducible memory leak when xcache.size is set too small to process a request	cloph	moo	"A Virtualbox image to reproduce the memory leak is available here:
http://buildbot-linux-1.documentfoundation.org/VMs/ (downloadsize around 380MB, extracted size ~1.1GB)

When xcache.size is set too a value too small to process a request, memory usage grows limitless, the bigger the difference between assigned and needed memory, the faster the memory usage grows.

Setup to reproduce:

* Apache with mod_fcgid, only one child process (to ensure all requests go to the same worker for ease of seeing the effect), and the default of 500 requests per process[[BR]]
* I use silverstripe as php-application to accelerate[[BR]]
* ab -n 499 http://localhost/ with xcache of 16M (i.e. large enough): no problem, everything is fine[[BR]]
* set xcache.size to value < 7M (that's approx. what is needed to process the homepage request in the blank setup), for example 4M[[BR]]
* restart apache or request the homepage once more to spawn a new worker that makes use of the changed setting[[BR]]
* ab -n 499 http://localhost/ once again, this time memory grows and grows until OOM-killer intervenes,

and it is not a couple of bytes with each request, it easily is more than one MB with each request."	defect	closed	major		cacher	1.3.0	fixed	memory leak xcache.size			5.3.2(suhosin)		FastCGI	Always