Clean up run loop shutdown callbacks#45
Merged
satoshi-szk merged 4 commits intoJun 22, 2026
Merged
Conversation
RunLoopGuard may be the last owner before a plugin DSO is unloaded, so shutdown must unregister native callbacks and drop queued work before returning.
Keep Linux sender cleanup source-based instead of retaining a callback queue, and make inactive handles explicit after shutdown.
Explain why platform shutdown must synchronously unregister native callbacks before plugin DSO unload.
Synchronize platform sender enqueue paths with shutdown so no native callback or queued closure can survive the final RunLoopGuard drop.
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.
Summary
Verification
Note: cargo clippy --workspace --all-targets -- -D warnings still fails on existing wry deprecated/unused-unsafe warnings unrelated to this change.