-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread safety question #217
Comments
I've never used Thread Sanitizer before so can't say why it gives such a warning. I'd suggest playing with a minimum code snippet that would use a recursive lock and recursive function calls if you are curious. It might be just a sanitizer not playing well with recursive locks. |
i do think there is a race condition here. the inContext function is protected by the lock, but also setting the context object.
the line at Resolve.swift ~ 141
is not protected by a lock and it is access the context object which is not protected. i think we need to protect the access to context?.resolvingType making the change below fix this issue, but i am not sure if this is the correct fix.
|
@ofirreuv72 is this still relevant? |
Hi,
enable thread sanitiser in Xcode.
I used the sample app provided and added this code.
in application didFinishLaunchingWithOptions after the configure function.
i am getting the error below
please advise
The text was updated successfully, but these errors were encountered: