docs(tech-debt): record fknm nanobind leak on background-thread creation#552
Merged
Conversation
Confirmed reproducible and independent of Swift/Ctrl+C: nanobind's leak detector fires for _ETObj/_ETSObj created via fkine()/jacob0() on a background thread, but not from thousands of the same calls on the main thread. Relevant to swift-sim, whose stepping runs off-thread.
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
1 participant
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
_ETObj/_ETSObjcreated viafkine()/jacob0()from a background thread get flagged as leaked at interpreter shutdown; the same calls on the main thread do not. Relevant toswift-sim, whose stepping runs off-thread.tech-debt.md), no code changes.Test plan