zaneclaes opened this Issue Nov 17, 2012 · 3 comments


None yet
3 participants

I cannot be 100% sure that this is the fault of the request module, and if I'm wrong I apologize, but it appears to be the case.

I'm having a scenario where my Node.js CPU becomes pegged while a request is being made. After the timeout expires, I get the following error:

Sat Nov 17 2012 08:48:11 GMT-0800 (PST): "Error: ETIMEDOUT\n at Object. (/home/webapps/SGPArray/releases/20121117084123/api/node_modules/request/main.js:670:15)\n at Timer.list.ontimeout (timers.js:101:19)

Once the error is fired, CPU usage drops back to normal.

umutm commented May 9, 2013

The same was happening to me when sending a GET request to a huge file (like a .zip file sized MBs).

The process was getting bigger and bigger as it was trying to keep the data in the memory and, once the timeouts happens, turning back to normal.

I solved it by limiting the request's body length. More info here: mikeal#488 .

Hope it helps.


mikeal commented May 9, 2013

this could be a memory usage issue. are you passing a callback or are you streaming?


mikeal commented Aug 27, 2014

Is this still an issue?

This is so old I'm closing, if it is actually still an issue just let me know and I'll re-open.

mikeal closed this Aug 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment