Prisma VSCode Plugin 2.27.0 memory leak/too many processes
See original GitHub issueBug description
There seems to be some sort of issue with v2.27.0 of vscode plugin where if it is enabled in VScode then when running yarn dev terminal will eventually start throwing errors like below.
I believe it has something to do with prisma plugin watching files for changes.
Reverting to v2.26.0 resolves the issue.
Error 1
zsh: fork failed: resource temporarily unavailable
Error 2
yarn dev
yarn run v1.22.10
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from /Users/user/Development/rc/ffs-dev/.env
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
events.js:292
throw er; // Unhandled 'error' event
^
Error: spawn /usr/local/bin/node EAGAIN
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -35,
code: 'EAGAIN',
syscall: 'spawn /usr/local/bin/node',
path: '/usr/local/bin/node',
spawnargs: [
'/Users/user/Development/rc/ffs-dev/node_modules/jest-worker/build/workers/processChild.js'
]
}
error Command failed with exit code 1.
How to reproduce
Steps to reproduce the behavior:
- Open VScode
- make sure prisma 2.27.0 vscode plugin is installed
- in terminal iterm2 or any other, run project with yarn dev
- Observer errors yarn dev will crash
- try to run yarn dev again notice the following error
zsh: fork failed: resource temporarily unavailable
- try running yarn dev again Observer the error
eady - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from /Users/user/Development/rc/ffs-dev/.env
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
events.js:292
throw er; // Unhandled 'error' event
^
Error: spawn /usr/local/bin/node EAGAIN
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -35,
code: 'EAGAIN',
syscall: 'spawn /usr/local/bin/node',
path: '/usr/local/bin/node',
spawnargs: [
'/Users/user/Development/rc/ffs-dev/node_modules/jest-worker/build/workers/processChild.js'
]
}
error Command failed with exit code 1.
- Kill vscode or install v2.26.0
- Notice that you can now run yarn dev and no issues are happening anymore
Expected behavior
Prisma information
Environment & setup
- OS: OSX Big Sur
- Editor:
Version: 1.58.2
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:09:06.581Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 20.5.0
- Extension version:v2.27.0
- Vscode has no other extensions installed
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Many processes and high memory usage in VSCode - VS Code
CPU reaches to 100% and memory usage is too high too on windows 10 ... When a VSCode window is closed, the extension...
Read more >Visual Studio Code took 10.7 GB RAM usage after using it for ...
It looks like there are many possible memory leak issues being tracked - but across several versions. Updated, I'm on the latest version....
Read more >Search Results - CVE
CVE-2021-42859, ** DISPUTED ** A memory leak issue was discovered in Mini-XML v3.2 that could cause a denial of service. NOTE: testing reports...
Read more >CHANGELOG.md · cellbang/malagu - Gitee.com
fix(serve-static) Fixes that when using the @malagu/serve-static component, the front-end build product is forced to be output to the non-memory file system ...
Read more >Untitled
Diffrazione della luce prisma, Maniquerville commerces, Video de asesinados con motosierra, ... Autofill firefox addon, Inspiron 9300 specs memory!
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Will try this weekend
The fix is now in the latest 4.4.0 version on the marketplace https://marketplace.visualstudio.com/items?itemName=Prisma.prisma 🎊
For those who disabled the File Watcher functionality, you can enable it again.