Oh and note that in our case, it's not a "sudden jump in usage, not a gradual leak" - the leak is progressive and *will* eat up all memory on the server eventually. After 30 seconds (the fastcgi timeout), the memory usage is around 1GB, iirc.
I am not sure it's FastCGI's responsability to cleanup that stuff - Apache connects to the fastcgi threads, which are usually long-lived. If they timeout once, that's not a good reason to kill them... I am not sure the solution proposed in #15108 is a good one as it would hide the problem in this case. A.
signature.asc
Description: Digital signature
