InternalError: too much recursion

[pine smelt]

Original message from Niklas

The error message I am seeing is invoke_iii@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:448886
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[1441]:0x12a4ce
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[1457]:0x12cd4f
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[110558]:0x2184d57
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[110443]:0x21753f5
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[135527]:0x2f05047
This is repeated until the maximum message length is reached.
My occasional reloads have also a couple of times yielded:
RuntimeError: indirect call to null
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[135253]:0x2ed8f55
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[135529]:0x2f0505f
unityFramework/Module.dynCall_viii@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:356545
JS_ScreenOrientation_eventHandler@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:45974

It might actually be related to a previous error I have come across. This error goes away with a refresh so it doesn't really block gameplay in the way that the top error does.
An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was:
TypeError: WebGL2RenderingContext.bufferData: Argument 2 can't be an ArrayBuffer or an ArrayBufferView larger than 2 GB
_glBufferData@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:271148
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[177]:0x0
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[130234]:0x2d8f54e
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[130151]:0x2d8aab2
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[130065]:0x2d7fc9a
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[134817]:0x2eb57a5
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[125138]:0x2aea6f9
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[125103]:0x2ae5034
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[131036]:0x2dff9b1
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[130985]:0x2deef29
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[130985]:0x2deef99
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[135503]:0x2eedd4c
@https://celltosingularity.com/play/Build/cells.wasm.gz:wasm-function[135531]:0x2f05077
browserIterationFunc@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:243468
callUserCallback@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:197037
runIter@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:198293
Browser_mainLoop_runner@https://celltosingularity.com/play/Build/cells.framework.js.gz:10:196573

[jovial siren]

Oh nice

[faint cedar]

had another popup regarding sound this time at the start

[dull thicket]

@faint cedar can you please also tell us your game version?

and are you playing on Android/IOS/Steam?

[faint cedar]

firefox

[dull thicket]

Please try switching your browser to something either chromium or safari-based and see if the error still occurs.

[faint cedar]

only happend once also ive got all sounds/music deactivated fyi

[manic matrix]

Above I mention the growing array that I thought might be related. Apparently this was not related as the original issue was solved but the max array size issue remains. I reposted that bug report as a separate issue but that was pointed back here and locked so I add some more info on that here.
The issue seems to be getting worse. It is not clear to me what data is leaking, but considering the size (2 GB) it seems to be something that should be easily identified. Just leaving the Beyond simulation open in a tab will produce this error. The reason why it hits the limit faster now might be that I have gotten further in the simulation so there is more data to keep track of. Should be fairly easy to reproduce in firefox with level 20 on everything.

[wet patrol]

on web version