Go-libsql app get killed over concurrent load

[bilalabdelkadir]

Go-libSQL app gets OOM killed under concurrent load

I tried connecting to libSQL from a Go app using multiple concurrent clients. On my Linux VPS, the process gets killed by the OOM killer.

• Exit code: 137
• RSS: 6.3 GB
• Virtual memory: 35 GB

How to reproduce

1. Create a new Go project and import go-libsql
2. Open a database connection
3. Spin up 6+ (increase the number upto 10 if it didn't fail) goroutines each running queries concurrently
4. Monitor memory with ps aux | grep <process> or htop
5. Observe memory spike and OOM killing it

Environment

• OS: Linux VPS (also tested on mac M4 same result)
• Go: 1.23.5
• go-libsql: v0.0.0-20251219133454-43644db490ff
• Project context: https://github.com/bilalabdelkadir/qlite

Question

Is this expected behavior for concurrent connections? My use case is a Postgres wire protocol proxy where many clients share one libSQL database ,which may be outside the typical single-app embedded use case.