Potential race condition in global trace
Open
@balupillai is already working on this.
Since Apr 6, 2026.
- Dominant language
- C
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Thread A created a object O. O->xref = notxref
Thread B references O and adds to its heap. O->xref = isxref
Global trace runs and flips notxref and isxref
Visits Thread A heap first. And marks O->xref = notxref
local_collection on Thread A will free O, while Thread B is still holding the reference.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.