fix: ensure env is not in an invalid state on shutdown#1442
Merged
Conversation
dunglas
approved these changes
Mar 14, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #1441
The issue is:
After releasing superglobals that have jit, they remain in an 'invalid state' as long as they are not reloaded (
$_SERVER,$_ENV,$_REQUEST). Since$_ENVis not reloaded in worker mode, accessing the global directly will lead to a segfault.Extensions like xdebug directly access the $_ENV global on shutdown.
This PR sets
$_ENVto an empty array on worker script shutdown to fix the segfault. Ideally,$_ENVwould not be released between requests, but I have not yet found a way to do so without causing a memory leak.