memory leak - with 2 in-memory databases in parallel running on linux
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9.2k
- Forks
- 1.2k
- Avg merge
- 19m
- Merged PRs (30d)
- 4
Description
please see https://github.com/sthielo/go-sqlite-memleak, where we stripped our code eventually terminating with an OutOfMemory exception using sqlite in-mem to produce what looks like a memory leak.
README gives some more explanations and observations, but one observation I would like to take upfront here: we only observe that problem on lilnux and not on windows.
We have no clue on the problems origin. Any help very much appreciated. Our code? Go-sqlite3 code? sqlite code?
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 with the linked go-sqlite-memleak repository and its README, then run the minimal in-memory database reproducer on Linux and Windows. Trace whether the leak belongs to go-sqlite3 or SQLite; done means the cause is identified and a reproducible fix or clear next action is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100