Invalid dest causes runaway node process
See original GitHub issueGiven the following code:
var express = require("express"),
multer = require("multer"),
app = express();
app.use(multer({dest: "h:\\drive\\does\\not\\exist"}));
I would expect an exception to be thrown stating that the destination does not exist.
Instead, the node process goes to 100% CPU and starts a runaway memory leak that very quickly locks up the system if not killed.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
runaway node process in neovim - Reddit
I am using NVIM v0.8.1 from Homebrew on a MacBook Air M2. Everything was fine until a couple of days ago. Now, I...
Read more >Let It Crash: Best Practices for Handling Node.js Errors on ...
In this post, I'll walk through some of the background on the Node.js process lifecycle and some strategies to properly handle graceful shutdown ......
Read more >Troubleshoot instances with failed status checks
The following information can help you troubleshoot issues if your instance fails a status check. First determine whether your applications are exhibiting ...
Read more >Callback Hell
Callback hell is caused by poor coding practices. Luckily writing better code isn't that hard! You only need to follow three rules: 1....
Read more >Node.js Handling invalid routes - GeeksforGeeks
It can be done by writing a custom route or redirecting all the invalid routes to any custom page. Create a separate folder...
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 FreeTop 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
Top GitHub Comments
Opened a PR w/ mkdirp to fix this on their 0.x branch https://github.com/isaacs/node-mkdirp/pull/15
This has been resolved with the publishing of
mkdirp 0.5.4
🎉