[GH-ISSUE #31] Adding a 2.5MB value gives "offset is out of bounds" error #28

New issue

Closed

opened 2026-05-23 08:26:35 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-23 08:26:35 -06:00

Owner

Originally created by @clibu on GitHub (May 17, 2021).
Original GitHub issue: https://github.com/appy-one/acebase/issues/31

Originally assigned to: @appy-one on GitHub.

I'm adding a value which is a "data:image/jpeg;base64,/...." which is approximately 2.5MB to AceBase v1.5.0 running in Node v16 and get the following repeatable error:

offset is out of bounds at 2021-05-17 14:33:55
        at Uint8Array.set (<anonymous>)
        at c:\webapps\clibuNotes\node_modules\acebase\src\storage-acebase.js:1526:21
        at c:\webapps\clibuNotes\node_modules\acebase\src\storage-acebase.js:1807:41

followed by non-stop:

read lock on path "/clibu_notes/kvigX6oc4vGkT9V4Gdqy7" by tid 2 (Node.getValue "/clibu_notes/kvigX6oc4vGkT9V4Gdqy7") is taking a long time to
complete [1]
...

Originally created by @clibu on GitHub (May 17, 2021). Original GitHub issue: https://github.com/appy-one/acebase/issues/31 Originally assigned to: @appy-one on GitHub. I'm adding a value which is a ` "data:image/jpeg;base64,/...."` which is approximately 2.5MB to AceBase v1.5.0 running in Node v16 and get the following repeatable error: ```` offset is out of bounds at 2021-05-17 14:33:55 at Uint8Array.set (<anonymous>) at c:\webapps\clibuNotes\node_modules\acebase\src\storage-acebase.js:1526:21 at c:\webapps\clibuNotes\node_modules\acebase\src\storage-acebase.js:1807:41 ```` followed by non-stop: ```` read lock on path "/clibu_notes/kvigX6oc4vGkT9V4Gdqy7" by tid 2 (Node.getValue "/clibu_notes/kvigX6oc4vGkT9V4Gdqy7") is taking a long time to complete [1] ... ````

gitea-mirror

2026-05-23 08:26:35 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-23 08:26:41 -06:00

Author

Owner

@appy-one commented on GitHub (May 18, 2021):

I've managed to reproduce the issue, and found where this is going wrong. Will be fixed shortly!

@appy-one commented on GitHub (May 18, 2021): I've managed to reproduce the issue, and found where this is going wrong. Will be fixed shortly!

gitea-mirror commented

2026-05-23 08:26:42 -06:00

Author

Owner

@appy-one commented on GitHub (May 19, 2021):

Fix published in v1.6.0

@appy-one commented on GitHub (May 19, 2021): Fix published in v1.6.0