Access violation when ALLOC_FALLBACK fixed #11304
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iluuu1994
approved these changes
May 24, 2023
There was a problem hiding this comment.
Thank you @KoudelkaB! Looks like an oversight. Can you please target/rebase onto the PHP-8.1 development branch?
|
Oh, and we also have the same issue here: Can you add it there as well? There other branches throw a fatal error and so are unproblematic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had a problem with using opcache on the second php-cgi.exe (the fallback to file op cache on the second process was triggered by different load addresses of PHP8.dll in both processes - this was ok so far)
But the fallback to file opcache was not working - when the cache was accessed it caused ACCESS VIOLATION because of wrong opcache globals pointer.