max-mapper / max-mapper/browser-csv-stream
there be memory leaks!
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
havent dug in yet to figure out why but it seems like this starts making Chrome mad when the CSVs are around 1 million + rows
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
Start by reproducing the issue in Chrome with CSVs of around one million rows, then inspect the browser-side streaming parser entry point. Use browser memory tools to identify what grows during parsing. Done means the parser can process these large CSVs without the reported memory leak or making Chrome unstable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100