A related issue was reported again in
https://github.com/igbinary/igbinary/issues/299 in PHP 7.4, Ubuntu 20.04
and igbinary 3.1.2, in the form of a reproducible segmentation fault for
ArrayObject.
There have been no changes to the igbinary v2 serialization format
itself - 3.1.6 and 3.1.2 should
We also were bitten by this bug. TYPO3 failed in weird problems because
reflection data could not be unserialized correctly. ("PHP Warning:
class_parents(): object or string expected [...] in DataMapper.php")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@tysona: Thank you very much for taking care of several PHP extensions!
This is much appreciated. JFTR I have updated php-igbinary in
ppa:ondrej/php and in Debian unstable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php-igbinary (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651031
This is made worse by the fact that installing php-redis causes php-
igbinary to be installed as well. In my case, we're running TYPO3 CMS
with redis for caching. The TYPO3 caching framework uses igbinary if
available and this breaks in really subtle ways. See
