in-memory database or 'backup to' seems to leak memory

未关闭
#307 5 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
java, sqlite
领域
databases

调研方向

Start by reading the issue’s report of the 10 GB off-heap increase during in-memory SQLite database creation and the 1.2 GB reduction after closing the connection and statement. Investigate the SQLite JDBC driver’s memory handling for in-memory databases and the backup to command; the issue does not name files or tests. Done means identifying whether memory remains allocated after resources are closed and how it can be released.

由索引模型根据 Issue 内容生成。

描述

bug help wanted

We are trying to create a large SQLite in-memory database and once the DB is created we are dumping it to a file using 'backup to' comand. This is done as creating a large in-memory sqlite db is much faster.

Once the backup process is complete, sqlite connection and statement is closed. When we looked at the memory footprint, the off-heap memory shot by 10GB during in-memory db creation. Once all the resources are closed, reduction in off-heap memory was around 1.2GB. We are left in 8.8GB extra memory in off-heap area.

So, we suspect a memory leak either in in-memory database or 'backup to'.
Is there a specific way to release memory for in-memory sqlite db?

主要语言
Java
星标
3.3k
派生
676
平均合并
1 天 15 小时
30 天内合并 PR
18

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

xerial/sqlite-jdbc 的其他 Issue

查看 xerial/sqlite-jdbc 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。