Mac OS 9.0.4 on a Power Mac G3 Beige just freezes after this.

[MesaBlack]

I got this after a while:

Emulator Error
The emulator encountered an error:

Array buffer allocation failed

[dingusdev]

Looking at the error log shows this:

emulator-worker-CTy6jlUh.js:1 RangeError: Array buffer allocation failed
    at new ArrayBuffer (<anonymous>)
    at new Uint8Array (<anonymous>)
    at Object.expandFileStorage (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:3197)
    at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:5322)
    at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:18300)
    at Qt (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48350)
    at en (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48452)
    at dingusppc.wasm.__stdio_write (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2497]:0xd0ada)
    at dingusppc.wasm.fflush (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2493]:0xd05ba)
    at dingusppc.wasm.loguru::file_log(void*, loguru::Message const&) (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2467]:0xcdd58)

So, it seems some flushing is preventing this from working. Let me see if I can fix that.

[MesaBlack]

'k

…

On Sun, Nov 24, 2024 at 4:22 PM dingusdev ***@***.***> wrote: Looking at the error log shows this: emulator-worker-CTy6jlUh.js:1 RangeError: Array buffer allocation failed at new ArrayBuffer (<anonymous>) at new Uint8Array (<anonymous>) at Object.expandFileStorage (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:3197) at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:5322) at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:18300) at Qt (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48350) at en (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48452) at dingusppc.wasm.__stdio_write (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2497]:0xd0ada) at dingusppc.wasm.fflush (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2493]:0xd05ba) at dingusppc.wasm.loguru::file_log(void*, loguru::Message const&) (wasm://wasm/dingusppc.wasm-0064c4f6:wasm-function[2467]:0xcdd58) So, it seems some flushing is preventing this from working. Let me see if I can fix that. — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7QFFJZJ2F4XBRHOAVYTQO32CJGSBAVCNFSM6AAAAABSMMAXVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGI3TKMZSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[MesaBlack]

at Object.expandFileStorage (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:3197)
at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:5322)
at Object.write (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:18300)
at Qt (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48350)
at en (https://infinitemac.org/assets/dingusppc-Cq_lcOGO.js:3:48452)

Do we need contact with mihai?

[MesaBlack]

currently still freezes.

[dingusdev]

Confirmed infinite loop due to DMA issues:

heathrow.cpp:161 WARN| Unsupported DMA channel write, offset=0x700, val=0x200020
heathrow.cpp:137 WARN| Unsupported DMA channel read offset=0x704