[php-src] Issue #7915: php_opcache crash - memory access violation
| From: | jjdunn | Date: | Tue, 11 Jan 2022 14:07:57 +0000 |
| Subject: | [php-src] Issue #7915: php_opcache crash - memory access violation | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-238965@lists.php.net to get a copy of this message | ||
Issue: https://github.com/php/php-src/issues/7915
Comment Author: jjdunn
> Hmm, I cannot reproduce that:
ah, yes. Sorry it was my mistake:
> php -d opcache.cache_id=%cli-cache% <entryScript.php> <processName1>
> <entryPoint1> <arguments>
I used your example literally, but did not have a variable %cli-cache% defined.
using a string literal like "2" or "clicache", I get the same results as you.
In my previous test, the cache_id variable was undefined, so functionally equivalent to null or
empty-string, which explains the previous results.
Sorry for the wasted effort on your part, and for my ignorance of Windows shell syntax.
I think the easy solution for me is to use the
-d opcache.cache_id=X option in all my
CLI processes, and omit opcache.cache_id from php.ini, so the web app gets the default cache.
This still does not explain php_opcache crashing, as per the subject of this ticket. I've been
monitoring for several days with opcache.log_verbosity_level=4; (*huge* log files); but
so far the crash has not happened.
I'll be offline from Jan 12 to Feb 12, so I'll return to this topic in a month.
Thank you again very much for your time, attention, expertise, and patience. :-)