You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a big deal, as the error happens in this case on PHP exit, the PHP code works, but maybe there are some other corner cases where this might be an issue.
…with opcache.file_cache_only=1 but it was never locked
I chose to check for the value of lock_file instead of checking the
file_cache_only, because it is probably a little bit faster and we're
going to access the lock_file variable anyway. It's also more generic.
* PHP-8.1:
Fix DOMElement::append() and DOMElement::prepend() hierarchy checks
Fix spec compliance error for DOMDocument::getElementsByTagNameNS
FixGH-11336: php still tries to unlock the shared memory ZendSem with opcache.file_cache_only=1 but it was never locked
FixGH-11338: SplFileInfo empty getBasename with more than one slash
* PHP-8.2:
Fix DOMElement::append() and DOMElement::prepend() hierarchy checks
Fix spec compliance error for DOMDocument::getElementsByTagNameNS
FixGH-11336: php still tries to unlock the shared memory ZendSem with opcache.file_cache_only=1 but it was never locked
FixGH-11338: SplFileInfo empty getBasename with more than one slash
Description
This is not a big deal, as the error happens in this case on PHP exit, the PHP code works, but maybe there are some other corner cases where this might be an issue.
will produce
It seems like the lock file is created here
https://github.com/php/php-src/blob/master/ext/opcache/zend_shared_alloc.c#L103
but this code is executed only when the file_cache_only=0
php-src/ext/opcache/ZendAccelerator.c
Line 3200 in 2d883a6
i.e. the lock file is not created with file_cache_only=1
but regardless of the file_cache_only directive, the code tries to unlock it and generates the error here
https://github.com/php/php-src/blob/master/ext/opcache/ZendAccelerator.c#L401
PHP Version
8.1.17
Operating System
Ubuntu 18.04
The text was updated successfully, but these errors were encountered: