-
Notifications
You must be signed in to change notification settings - Fork 229
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
Deadlock due to race in FsEventWatcher #118
Labels
Comments
@michaelfairley are you okay with me using your workaround? |
Yes! Please do! It's been working well enough for me since I initially filed this issues. |
@michaelfairley are you in a position to PR your patch? If not I can, save @passcod the time. |
Done with #134 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because the runloop thread signals that the runloop has started before
CFRunLoopStart
is called, it's possible forCFRunLoopStop
to get called beforeCFRunLoopStart
, causing the runloop to never stop and thus thedone
channel to be waited on forever.In practice, if I have two
watch
commands back to back, I get a deadlock roughly 10% of the time on my Mac.I have a somewhat cheesy workaround that I'm using right now, but an ideal solution probably involves
CFRunLoopObserver
or somesuch.The text was updated successfully, but these errors were encountered: