tursodatabase / tursodatabase/libsql
Memory leak, Dockerized on Railway
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
This is the memory usage pattern for my 35Mb SQLite DB running on LibSQL in a container on Railway. Over time the memory usage just grows and grows.
If I restart the container, the usage drops dramatically.
Is there a known issue running in Docker containers with memory leaking?
Contributor guide
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
The issue names no source files, tests, or entry points. Start by reproducing the reported 35 MB SQLite database workload in a libSQL Docker container on Railway and compare memory growth over time with usage after a restart. Done means identifying whether the behavior is a libSQL leak and documenting or fixing its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, sqlite
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100