tursodatabase / tursodatabase/libsql-js
Memory leak
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
During benchmarking of libsql-js I discovered a memory leak.
Code to reproduce issue:
https://github.com/mapka-dev/mbtiles-benchmark/blob/master/libsql-node-js/default-seq.js
Memory increased to total of 23GB. Once all queries completed, it went back to normal values.
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 running the reproduction in mbtiles-benchmark/libsql-node-js/default-seq.js and observe memory usage while its queries complete. Trace the behavior through libsql-js and compare memory before and after the benchmark; done means the reproduction no longer grows to 23GB and memory returns normally without an unexplained leak.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, sqlite
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100