Memory consumption

[silverwind]

This might be more of an v8/node issue, but I'm banging my head on why busboy and other multipart parsers (namely, I've tried formidable and multiparty) seem to make v8 unable to garbage collect uploaded data.

Here's my test case, which can be run locally: https://gist.github.com/silverwind/10f076397348a64a72a5

When uploading a 3.4 GB file, the process first starts out at around 45 MB, then quickly climbs to to size of the uploaded file at 3.5 GB. At this point, the file is written to the disk completely, but the process doesn't go down a bit in memory consumption until killed. At this point, I tried to upload the same file again. My machine with 4 GB + 4 GB swap froze up pretty badly at this point, last I saw it was at around 6.5 GB explicit memory on the node process. I was eventually able to kill the node process, here's how the memory history looked:

Note that the graph above is a bit misleading. The explicit consumption of the node process never went down until killed. I think it's the OS making some on-demand memory available, but that's just a guess.

By the way, this is on io.js 3.0.0, but I assume all versions to be affected.

[silverwind]

drumroll turns out that this is most likely an io.js/v8 issue as node 0.12.7 is not affected. Now to narrow it down. Edit: io.js 2.5.0 is good, 3.0.0 has it.

[silverwind]

Closing as this isn't an issue with this module.