Getting an error on Memory access out of bounds when trying to run db.exec with a large query string

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
javascript, sqlite, wasm
领域
databases

调研方向

Reproduce the failure in Google Chrome with SQL.js 1.8.0 using a db.exec query around 1.5 MB, then compare it with a smaller query that succeeds. Determine whether the behavior is a documented query-size limit or a defect, and document the limit or provide a verified fix.

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

描述

When creating the database initially, we use a large file that is successfully processed to create the database.
Afterwards, when we attampt to run a script to add another table, it is throw the error Memory access out of bounds.

This always happens when the query string is about 1.5MB.
When the query is below that size, the query is successfully processed and the database is updated with the new table.

Is there a limit to much much the query string should be big?

This is was done Google Chrome browser version 120.0.6099.224 64bits
On SQL.js library version ^1.8.0

主要语言
JavaScript
星标
13.7k
派生
1.1k
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

sql-js/sql.js 的其他 Issue

查看 sql-js/sql.js 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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