Potential race condition in global trace

Open
#15 0 comments 0 reactions 1 assignee View on GitHub

@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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SparkPost/thrlua

All issues in SparkPost/thrlua

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.