some users have reported that XCache might make php 5.2 coredump after ran for a long time, leaving "zend_mm_heap corrupted" in the log. this is now known as compatibility issue now. luckily we have a workarround: set xcache.mmap_path = /tmp/xcache xcache.readonly_protection = on in your php ini the key is to turn on readonly_protection, but with xcache.mmap_path=/dev/zero, readonly_protection is not available we'll be working on this issue http://trac.lighttpd.net/xcache/ticket/90
on 28.04.2007 11:51
on 28.04.2007 21:15
moo XCache wrote: > some users have reported that XCache might make php 5.2 coredump after > ran for a long time, leaving "zend_mm_heap corrupted" in the log. > > this is now known as compatibility issue now. luckily we have a > workarround: > > set > xcache.mmap_path = /tmp/xcache > xcache.readonly_protection = on > in your php ini > > the key is to turn on readonly_protection, but with > xcache.mmap_path=/dev/zero, readonly_protection is not available > > we'll be working on this issue > http://trac.lighttpd.net/xcache/ticket/90 FYI: I have not experienced this issue at all...
on 30.04.2007 16:36
> FYI: I have not experienced this issue at all...
Neiter.
on 21.02.2008 01:50
Guest wrote: >> FYI: I have not experienced this issue at all... > > Neiter. I did
on 14.03.2008 09:07
Hamza Aboulfeth wrote: > Guest wrote: >>> FYI: I have not experienced this issue at all... >> >> Neiter. > > I did see http://forum.lighttpd.net/topic/42805#new
