Skip to content

Fix a potential use-after-free - #70

Merged
skeet70 merged 1 commit into
mainfrom
fix-async-cancel-use-after-free
Sep 16, 2026
Merged

skeet70 merged 1 commit into
mainfrom
fix-async-cancel-use-after-free

Conversation

@skeet70

@skeet70 skeet70 commented Sep 16, 2026

Copy link
Copy Markdown
Member

CI finally hit it, and we had a bunch of thoughts about how it was theoretically not possible in the comments. Fix, and tests to regression cover it (that were able to more reliably recreate the problem).

CI finally hit it, and we had a bunch of thoughts about how it
was theoretically not possible in the comments. Fix, and tests
to regression cover it (that were able to more reliably recreate
the problem).
@skeet70
skeet70 requested a review from a team as a code owner September 16, 2026 17:18
@skeet70
skeet70 requested review from coltfred and giarc3 and removed request for a team and coltfred September 16, 2026 17:18
@github-actions

Copy link
Copy Markdown

File Coverage Lines
All files 91% 91%

Minimum allowed coverage is 0%

Generated by 🐒 cobertura-action against 3ee0c29

@skeet70
skeet70 merged commit bf9c494 into main Sep 16, 2026
6 checks passed
@skeet70
skeet70 deleted the fix-async-cancel-use-after-free branch September 16, 2026 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants