search

4ian / GDevelop

🎮 Open-source, cross-platform 2D/3D/multiplayer game engine designed for everyone.
https://gdevelop.io
Other
10.82k stars 848 forks source link

error with file watchers in dev environment w electron #1606

Closed blurymind closed 4 years ago

blurymind commented 4 years ago

Describe the bug

I keep getting this warning

{/home/fox/DEV/GDevelop/GDJS/Runtime: Error: ENOSPC: no space left on device, watch '/home/fox/DEV/GDevelop/GDJS/Runtime'
    at FSWatcher…, /home/fox/DEV/GDevelop/GDJS/Runtime/Cocos2d: Error: ENOSPC: no space left on device, watch '/home/fox/DEV/GDevelop/GDJS/Runtime/Cocos2d'
    at F…, /home/fox/DEV/GDevelop/GDJS/Runtime/Cordova: Error: ENOSPC: no space left on device, watch '/home/fox/DEV/GDevelop/GDJS/Runtime/Cordova'
    at F…, /home/fox/DEV/GDevelop/GDJS/Runtime/Electron: Error: ENOSPC: no space left on device, watch '/home/fox/DEV/GDevelop/GDJS/Runtime/Electron'
    at …, /home/fox/DEV/GDevelop/GDJS/Runtime/FacebookInstantGames: Error: ENOSPC: no space left on device, watch '/home/fox/DEV/GDevelop/GDJS/Runtime/FacebookInstantGa…, …}

The thing is I have over 2 gb left in home and plenty on root. What is worse, when I get this warning, editing the code of the ide or extensions doesnt update gdevelop that is running, I have to literally stop it and wait for it like 5 minutes to restart to see my changes

I dont get the warning in the server, I get it on electron

Other details

Linux

blurymind commented 4 years ago

This could be some funkiness with my manjaro. I noticed I have a folder in my home dir named ¬ set to root. Deleting it seems to have stopped this, although that hardly makes any sense

4ian commented 4 years ago

Definitely looked like some permission/weird file system issue (like a read only file system).

blurymind commented 4 years ago

reopening this, as I'm getting the issue again. This time that folder doesnt even exist.

It makes development really slow. I was going to try in windows, but my windows installation is borked atm

blurymind commented 4 years ago

I have a strong feeling that it has to do with my max file watchers setting on linux

cat /proc/sys/fs/inotify/max_user_watches
16384

cat /etc/sysctl.conf
fs.inotify.max_user_watches=524288

If I edit cat /etc/sysctl.conf with nano and reduce the number, that might fix it

blurymind commented 4 years ago

This was indeed the issue. Closing this now