Avoid crash on traffic_server shutdown #9792
Merged
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
Member
Author
|
[approve ci] |
bneradt
approved these changes
Jun 7, 2023
Contributor
bneradt
left a comment
bneradt
left a comment
There was a problem hiding this comment.
I'm glad you found this.
The crash is occasioned by some updated system package. The old CI image worked fine, but if you do a sudo yum update on the old image, the certifier test starts crashing again.
I suggest we:
- Pull in this patch so the crash stops for now.
- Update the CI image with the newer packages.
- File an issue for the crash and push to get it assigned and worked on.
bneradt
added a commit
to bneradt/trafficserver
that referenced
this pull request
Nov 19, 2025
Remove the commented-out debug statement from the SslData destructor. This statement was commented out in PR apache#9792 as a stop-gap measure because it was causing crashes during shutdown when accessing the potentially-destroyed dbg_ctl static object. Let's close the associated issue by just removing the commented out debug statement since it is generally considered unsafe to log in a destructor precisely because of its use of static structures which can surface order-dependent issues like the one reported in apache#9794. That is, not logging in the destructor is the correct solution, so let's just make @maskit's patch official. Fixes: apache#9794
bneradt
added a commit
that referenced
this pull request
Nov 20, 2025
Remove the commented-out debug statement from the SslData destructor. This statement was commented out in PR #9792 as a stop-gap measure because it was causing crashes during shutdown when accessing the potentially-destroyed dbg_ctl static object. Let's close the associated issue by just removing the commented out debug statement since it is generally considered unsafe to log in a destructor precisely because of its use of static structures which can surface order-dependent issues like the one reported in #9794. That is, not logging in the destructor is the correct solution, so let's just make @maskit's patch official. Fixes: #9794
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.
No description provided.