smoldot 2.0.33 → 2.0.35

package/dist/cjs/internals/local-instance.js

@@ -364,8 +364,10 @@ function startLocalInstance(config, wasmModule, eventCallback) {
             peekJsonRpcResponse: (chainId) => {
                 if (!state.instance)
                     return null;
-                const mem = new Uint8Array(state.instance.exports.memory.buffer);
                 const responseInfo = state.instance.exports.json_rpc_responses_peek(chainId) >>> 0;
+                // Note that the memory must be created after calling the Wasm function, otherwise
+                // it might be invalidated if it is grown.
+                const mem = new Uint8Array(state.instance.exports.memory.buffer);
                 const ptr = buffer.readUInt32LE(mem, responseInfo) >>> 0;
                 const len = buffer.readUInt32LE(mem, responseInfo + 4) >>> 0;
                 // `len === 0` means "queue is empty" according to the API.
@@ -389,7 +391,7 @@ function startLocalInstance(config, wasmModule, eventCallback) {
                 console.assert(disableJsonRpc || jsonRpcMaxPendingRequests != 0, "invalid jsonRpcMaxPendingRequests value passed to local-instance::addChain");
                 // `add_chain` unconditionally allocates a chain id. If an error occurs, however, this chain
                 // id will refer to an *erroneous* chain. `chain_is_ok` is used below to determine whether it
-                // has succeeeded or not.
+                // has succeeded or not.
                 state.bufferIndices[0] = new TextEncoder().encode(chainSpec);
                 state.bufferIndices[1] = new TextEncoder().encode(databaseContent);
                 const potentialRelayChainsEncoded = new Uint8Array(potentialRelayChains.length * 4);

package/dist/cjs/public-types.d.ts

@@ -351,7 +351,7 @@ export interface AddChainOptions {
      * inspecting the chain specification of that parachain (i.e. the `chainSpec` field).
      *
      * This poses a problem in situations where the same client is shared between multiple different
-     * applications: multiple applications could add mutiple different chains with the same `id`,
+     * applications: multiple applications could add multiple different chains with the same `id`,
      * creating an ambiguity, or an application could register malicious chains with small variations
      * of a popular chain's `id` and try to benefit from a typo in a legitimate application's
      * `relayChain`.