I'm seeing frequent exceptions from Unity's main rendering loop in WASM-compiled WebGL players. I'm using Unity 2020.1. I'll create a support ticket but I want to get this information out there for other developers who may be impacted. Behavior: Unity's WebGL player will randomly crash the WASM runtime with a fatal "memory access out of bounds" error. It doesn't happen in the editor or PC/Desktop builds. The stacktrace shows it is internal to a material pass and render. ApplyMaterialPassAndKeywordsWithCache I suspect the issue can be remedied by turning off dynamic batching. Will try and report back here.