dogsheep / dogsheep/google-takeout-to-sqlite
killed by oomkiller on large location-history
Open
bug
- Dominant language
- Python
- Stars
- 121
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
memory seems to grow unbounded and is oom-killed after about 20GB memory usage.
this is happening while loading a ~1GB uncompressed location history.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure while loading a roughly 1GB uncompressed location history, monitoring memory until the process is killed near 20GB. Trace the location-history loading path and identify where memory grows; done means the same input completes without unbounded growth or an OOM kill.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100