Nodejs memory leaks on cancelling download with download manager

Question

I created a simple file downloader using Expressjs 3 and Nodejs 0.10

function download(req, res, filepath, filename){
    res.header('Content-Type', 'application/force-download');
    res.header('Content-Type', 'application/octet-stream');
    res.attachment(filename);
    res.download(filepath, filename);
}

Everything is OK, but when I test application with download managers (for example Internet Download Manager), when I abort or cancel download (before or during download), it throws a warning:

Trace
    at Socket.EventEmitter.addListener (events.js:160:15)
    at Socket.Readable.on (_stream_readable.js:653:33)
    at Socket.EventEmitter.once (events.js:179:8)
    at TCP.onread (net.js:512:26)

(node) warning: <b>possible EventEmitter memory leak detected. 11 listeners added. Use
emitter.setMaxListeners() to increase limit.</b>

How can I remove listener after aborting file download?

Answered [here](http://stackoverflow.com/a/9768586/893780). – robertklep Mar 13 '13 at 19:00 — robertklep, Mar 13 '13 at 19:00

score 0 · Accepted Answer · edited Jun 25 '15 at 12:53

0

The problem is solved
Add setMaxListeners(0) after Expressjs definition:

var express = require('express');

//expressjs 2.x
//var app = module.exports = express.createServer();

//expressjs 3.x
var app = module.exports = express();

//ADD BELOW CODE
app.setMaxListeners(0);

Thanks to @robertklep

edited Jun 25 '15 at 12:53

Manwal

23,450
12
63
93

answered Mar 17 '13 at 09:56

raminious

161
1
5

This simply removes the limit of listeners that can attach to an `EventEmitter`. The question was about removing event listeners. – nikc.org Aug 10 '13 at 08:23
Yeah, you still have the event listeners there, all you did was suppress the warning messages. – jemiloii Jul 19 '16 at 19:50

Nodejs memory leaks on cancelling download with download manager

1 Answers1