Repository navigation
Fix threaded compile cache cleanup - #3628
Merged
zcbenz merged 2 commits intoJun 5, 2026
Merged
Conversation
zcbenz
approved these changes
Jun 4, 2026
zcbenz
left a comment
zcbenz
left a comment
Member
There was a problem hiding this comment.
This fix looks good to me, thanks!
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
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.
When mx.compile is used as a decorator but the compiled function is first invoked on another thread, the invocation thread’s compiler cache could keep Python output metadata until unsafe thread teardown. This change makes sure we register cache cleanup in the invoking thread too.
Resolves #3619
Checklist
Put an
xin the boxes that apply.pre-commit run --all-filesto format my code / installed pre-commit prior to committing changes