Multi thread issue in 'leak_enabled_check'. #27
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.
Hi,
After using the library intensively on a program, I noted some weird unexpected traces in the log file:
Investigating what could cause it, it turned out there is threading issue in function 'leak_enabled_check': when accessed concurrently, the method sets temporarily the static variable 'leak_enabled' to false, which affects the other threads running.
Here is a test code I used to reproduce the issue (with variable LEAK_PID_CHECK=1):
No issue when code is run on a single thread, while some "may-leak" are randomly reported when using more threads.