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 }}
Repository navigation
InotifyBackend hungs forever when inotify_init1 returns error #159
The fix will require a bit more than just calling mStartedSignal.notify() (error needs to be populated up the stack) - the above just highlights in what state the process ends up when this error happens.
Steps to reproduce
Setup simple parcel project (package.json + src/index.js is sufficient)
Set /proc/sys/fs/inotify/max_user_instances to some small value (e.g. 1)
Naturally the problem of too many inotify instances needs to be fixed (even when this bug will be resolved) - either by closing old processes in system or by increasing the limit echo 256 | sudo tee /proc/sys/fs/inotify/max_user_instances (default is often 128).
Activity
[-]InotifyBackend hungs forever when [/-][+]InotifyBackend hungs forever when inotify_init1 returns error[/+]jsimomaa commentedon Jan 23, 2024
(Just as FYI for possible crawlers with the same problem than I had)
I encountered this bug as well during a
gatsby build:And stuck here forever. GDB helped me to trace the issue here: