You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
When Atom launches with experimental watchers enabled, occasionally the entire process stalls and Atom stops responding to mouse or keyboard input. There doesn't appear to be any watcher code on the stack when it's sampled with Activity Monitor.
I'm wondering if this is a bug in the NativeWatcherRegistry.
From my anecdotal observations it would seem that after setting the env vars described in #123 the stalls no longer occur upon launch. I set the log destinations to /dev/null for the main and worker processes/threads.
Atom-Beta 1.29-beta.2
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When Atom launches with experimental watchers enabled, occasionally the entire process stalls and Atom stops responding to mouse or keyboard input. There doesn't appear to be any watcher code on the stack when it's sampled with Activity Monitor.
I'm wondering if this is a bug in the NativeWatcherRegistry.
Observed by both @as-cii and @maxbrunsfeld.
The text was updated successfully, but these errors were encountered: