On 06.11.2019 at 14:02, Christoph M. Becker wrote: > while having had a closer look at <https://bugs.php.net/78754>, I > learned that OPcache's file_cache is prone to some configuration > changes, which may cause PHP segfaults (and maybe other malfunctions). > For instance, if Xdebug is enabled while a file is compiled, but later > disabled when executing that file, the process is segfaulting because > the cached file relies on user opcode handlers which are no longer > available without Xdebug loaded. I'm presenting Xdebug as example > because that likely caused the issues reported in that ticket, but > basically any extension can call zend_set_user_opcode_handler() to > install user opcode handlers, causing the same problems. > > It should be mentioned that, to my knowledge, shared memory caches are > not affected by this (except for Windows), because re-attaching a > differently configured php instance isn't possible at all. > > Anyhow, should we fix this (assuming a general fix would be possible), > or would that be rather a documentation issue, based on the assumption > that such configuration changes don't make sense in combination with > OPcache at all (IOW, if such changes are done, users should reset OPcache)..
Any thoughts regarding this issue? -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
