1 reply

Hi.

Hi.
I'm seeing a strange behavior of wasm in DurableObjects, especially when alarms are used. I saw this exception in logs before we were using alarms (when response was synchronous), but now it started happenning very often.

The library used is automerge.
After a DO gets into a "broken state", an exception is raised for any library method call in the code produced by wasm-bindgen:

RangeError: Invalid typed array length: undefined\n at new Uint8Array (<anonymous>)\n at getUint8Memory0

let cachedUint8ArrayMemory0 = null;
function getUint8ArrayMemory0() {
    if (cachedUint8ArrayMemory0 === null || cachedUint8ArrayMemory0.byteLength === 0) {
        cachedUint8ArrayMemory0 = new Uint8Array(wasm.memory.buffer);
    }
    return cachedUint8ArrayMemory0;
}

let cachedUint8ArrayMemory0 = null;
function getUint8ArrayMemory0() {
    if (cachedUint8ArrayMemory0 === null || cachedUint8ArrayMemory0.byteLength === 0) {
        cachedUint8ArrayMemory0 = new Uint8Array(wasm.memory.buffer);
    }
    return cachedUint8ArrayMemory0;
}

wasm.memory.buffer

wasm.memory.buffer

if logged is an ArrayBuffer with non-zero byteLength.
The exception logs spikes on

wrangler deploy

wrangler deploy

s (attached screenshot). But happens during the normal execution as well. I don't yet understand how a DO gets into and out (the guess is when it gets recreated in another process (isolate?)) of this state, but once it does it keeps failing on any library operations.
Would appreciate any ideas or hints on what might be the problem.

Hi.

RangeError: Invalid typed array length: undefined\n at new Uint8Array (<anonymous>)\n at getUint8Memory0

let cachedUint8ArrayMemory0 = null;
function getUint8ArrayMemory0() {
    if (cachedUint8ArrayMemory0 === null || cachedUint8ArrayMemory0.byteLength === 0) {
        cachedUint8ArrayMemory0 = new Uint8Array(wasm.memory.buffer);
    }
    return cachedUint8ArrayMemory0;
}

let cachedUint8ArrayMemory0 = null;
function getUint8ArrayMemory0() {
    if (cachedUint8ArrayMemory0 === null || cachedUint8ArrayMemory0.byteLength === 0) {
        cachedUint8ArrayMemory0 = new Uint8Array(wasm.memory.buffer);
    }
    return cachedUint8ArrayMemory0;
}

wasm.memory.buffer

wasm.memory.buffer

if logged is an ArrayBuffer with non-zero byteLength.
The exception logs spikes on

wrangler deploy

wrangler deploy

Hi.

Similar Threads

Hi.

Similar Threads

Similar Threads

Similar Threads