max-mapper / max-mapper/csv-write-stream
Looks like memory leak
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 203
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I've started bench.js, but for 200 000 000 iterations and application has crashed with out of memory error.
I've tested on Win7 x64, node 4.2.2, csv-write-stream 2.0.0
<--- Last few GCs --->
```
8867 ms: Scavenge 1401.9 (1456.4) -> 1401.9 (1456.4) MB, 3.5 / 0 ms (+ 8.0 m
```
s in 1 steps since last GC) [allocation failure] [incremental marking delaying m
ark-sweep].
9786 ms: Mark-sweep 1401.9 (1456.4) -> 1401.9 (1456.4) MB, 919.0 / 0 ms (+ 2
10.0 ms in 1914 steps since start of marking, biggest step 8.0 ms) [last resort
gc].
10698 ms: Mark-sweep 1401.9 (1456.4) -> 1401.9 (1456.4) MB, 912.0 / 0 ms [las
t resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 00000152EE9373A9
1: nextTick [node.js:~477] [pc=00000287435F95FE](this=00000152EE9B7CF1 ,callback=00000190EDC954B9 1
3: onwrite(aka onwrite) [_stream_writable.js:~314] [pc=00000287435E7C1E] (th
is=00000152EE904131 ,stream=00000190EDCC8619 ,er=000...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with bench.js using Node 4.2.2 and csv-write-stream 2.0.0 for 200,000,000 iterations, while monitoring memory and reviewing the reported stream stack trace. Done means the out-of-memory behavior is explained and verified as resolved or documented as a limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100