Last test :
I think I've found the culprit, a single non acsii character… still a huge bug if you can't post uft8 characters…
Here's the message :
Just crashed again with 600MB. I've reducted it to 500M to see but am thinking about giving eaccelerator a try.
This is a pain, I wanted to allow 30GB originaly for opcode cache and varcache.
I had some strange crashing with PHP creating core dumps of 2GB (maximum memoy CloudLinux is set to allow for accounts. I suppose it's something to do with processes being shared accross accounts but each time PHP has made litespeed crash there have been quite a few coredumps before. Could there be a more global memory issue ? It's normal to see xcache in any core dump as scripts are cached…
Dam, can't seem to get my full post to save, only happens on litespeed's forum, I guess could be litespeed cache issue ?