Potential race condition in global trace
@balupillai is already working on this.
Since Apr 6, 2026.
Assessment
This issue has not been assessed yet.
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.
- Dominant language
- C
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from SparkPost/thrlua
All issues in SparkPost/thrlua
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·