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
This is a very strange issue that I've been running into sporadically.
Very rarely, on startup, Process.spawn calls don't spawn anything. However, the config isn't deadlocked or anything because doing something like triggering a keybind causes all the processes to get spawned at once, like unblocking a clog.
The second time it happened I looked at the logs and it seemed like the spawn calls weren't even received by the compositor, like the gRPC calls are backing up config-side.
The text was updated successfully, but these errors were encountered:
This is a very strange issue that I've been running into sporadically.
Very rarely, on startup,
Process.spawn
calls don't spawn anything. However, the config isn't deadlocked or anything because doing something like triggering a keybind causes all the processes to get spawned at once, like unblocking a clog.The second time it happened I looked at the logs and it seemed like the spawn calls weren't even received by the compositor, like the gRPC calls are backing up config-side.
The text was updated successfully, but these errors were encountered: