[horde] trap invalid opcode/segfault in horde_lz4

Patrick Domack patrickdk at patrickdk.com
Tue Sep 23 22:38:27 UTC 2014

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>> Zitat von Patrick Domack <patrickdk at patrickdk.com>:
>>> I just updated horde_lz4 yesterday, and am having endless log  
>>> entries about this. I didn't have any of these before I updated,  
>>> and was running the release from when v5.2.0 horde was released.
>>> As to be expected, disabling horde_lz4, cleaned out the crashes.
>>> php5-fpm[30515] trap invalid opcode ip:7f8f9ddb96b0  
>>> sp:7fff7bbb93f8 error:0 in horde_lz4.so (deleted)[7f8f9ddb8000+8000]
> About 99% sure you updated without restarting PHP (that's what the  
> (deleted) means).

Makes sense, except I manually always restart memcached and php after  

There are log entries without the (deleted) part in it too.

I just re-enabled it, I'll do some more testing and see if the problem  
persists, or if it was just an artifact of during the upgrade process.

More information about the horde mailing list