Repository navigation
Tell users what happens when the Wasm memory runs out, and how to avoid it - #185
Merged
Merged
Conversation
CoverageFor 7acd76f. |
…id it - Describe the error a caller sees, a RuntimeError rather than a JetdbError, with nothing logged - Describe that the Database whose method ran out cannot be used or freed after it, and that the module should be loaded again - Describe how to avoid it: read large tables in parts, and free databases or open them with using - Add a section to docs/wasm in English and Japanese, and a summary to the README of jetdb-wasm Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
dominion525
force-pushed
the
docs/wasm-out-of-memory
branch
from
October 26, 2026 18:19
c257b16 to
7acd76f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RuntimeError(unreachablein Node.js), not aJetdbError, and nothing is logged.free()of that Database throw and its memory is not released, so the module should be loaded again. This was reproduced on Node.js; other open Databases kept working.limitandstartoptions ofrows, and to free each Database or open it withusingrather than leave it to the garbage collector.🤖 Generated with Claude Code