Skip to content

Conversation

@OleksiiiSemko
Copy link

@OleksiiiSemko OleksiiiSemko commented Dec 12, 2023

Fix of the #28 issue.
The Callstack structure is reset inside the CaptureContext destructor and deleted inside the unmap method. CaptureContext destructor and unmap method can be called in separate threads but std::unordered_map restore method is not threadsafe and the call is not protected by the critical section, because of this the Callstack destructor can be called twice for the same object.

@Neustradamus
Copy link

@OleksiiiSemko, @mattdurak: Any progress on it?

@mattdurak
Copy link

Seems safe, likely we would need to validate it for our use case, FYI @dcristoloveanu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants