That's the same spot that it crashed for me with an error about Unity accessing an out-of-bounds memory location. I wasn't noticing any performance issues prior to that, though.
I'm playing in Chrome (Version 143.0.7499.41) on a laptop running Windows 11 with 32 GB of RAM.
Same here. this is the error:
WebBuild6.framework.js.br:4300 Uncaught exception from main loop:
_JS_CallAsLongAsNoExceptionsSeen @ WebBuild6.framework.js.br:4300
$func171264 @ WebBuild6.wasm.br:0x3439bfe
$dynCall_v @ WebBuild6.wasm.br:0x346b007
browserIterationFunc @ WebBuild6.framework.js.br:4300
callUserCallback @ WebBuild6.framework.js.br:4300
runIter @ WebBuild6.framework.js.br:4300
Invoking error handler due to
RuntimeError: memory access out of bounds
at WebBuild6.wasm.br:0x23976e2
at WebBuild6.wasm.br:0x346b039
at invoke_viii (WebBuild6.framework.js.br:4300:511231)
at WebBuild6.wasm.br:0x23994e7
at WebBuild6.wasm.br:0x236af9e
at WebBuild6.wasm.br:0x2612fbd
at WebBuild6.wasm.br:0x2641a60
at WebBuild6.wasm.br:0x346afff
at invoke_iiii (WebBuild6.framework.js.br:4300:511081)
at WebBuild6.wasm.br:0x2640a39
at WebBuild6.wasm.br:0x1831ff
at WebBuild6.wasm.br:0x3377222
at WebBuild6.wasm.br:0x26764fa
at WebBuild6.wasm.br:0x2676430
at WebBuild6.wasm.br:0x32adee4
at WebBuild6.wasm.br:0x320e6db
at WebBuild6.wasm.br:0x331bac2
at WebBuild6.wasm.br:0x331bb37
at WebBuild6.wasm.br:0x3439ae9
at WebBuild6.wasm.br:0x346b007
at WebBuild6.framework.js.br:4300:23505
at _JS_CallAsLongAsNoExceptionsSeen (WebBuild6.framework.js.br:4300:23519)
at WebBuild6.wasm.br:0x3439bfe
at WebBuild6.wasm.br:0x346b007
at browserIterationFunc (WebBuild6.framework.js.br:4300:115630)
at callUserCallback (WebBuild6.framework.js.br:4300:97992)
at Object.runIter (WebBuild6.framework.js.br:4300:99359)
at Browser_mainLoop_runner (WebBuild6.framework.js.br:4300:115156)