max listeners exceeded in Node when benchmarking Next
Unanswered
Himalayan posted this in #help-forum
HimalayanOP
How to reproduce on macOS:
Install Next.
Build.
Run via start.
Benchark in other terminal window e.g.:
After the test is done, go back to the terminal where you did npm run start.
Now you won't be able to exit the running npm run start Next process using CTRL+C.
Also after a few presses of ctrl+c you could be shown a Node error message that the max. listeners were exceeded in Node.
Is this a feature or a bug? It's a serious question. Ireally don't know if it's my responsibility to find a place in Next and set the limit or something or it's not possible or what.
Thanks for any advice.
Also, I am super interested if you are experiencing the same terminal "lock out" as I do or it's something specific to my Macbook version or something.
Install Next.
Build.
Run via start.
Benchark in other terminal window e.g.:
wrk -t2 -c400 -d10s http://127.0.0.1:3000After the test is done, go back to the terminal where you did npm run start.
Now you won't be able to exit the running npm run start Next process using CTRL+C.
Also after a few presses of ctrl+c you could be shown a Node error message that the max. listeners were exceeded in Node.
Is this a feature or a bug? It's a serious question. Ireally don't know if it's my responsibility to find a place in Next and set the limit or something or it's not possible or what.
Thanks for any advice.
Also, I am super interested if you are experiencing the same terminal "lock out" as I do or it's something specific to my Macbook version or something.
3 Replies
HimalayanOP
Hmm, in iterm2 I was able to exit it via ctrl+c.
It's perhaps something related to VS Code.
It's perhaps something related to VS Code.
Can anybody try it in their VS Code and outside of VS Code in the default terminal or other terminal emulator?
Another reason to try Zed I guess.