We’re tracing down an occasional crash that occurs in a long-running session. When it occurs, the Babylon scene freezes (but HTML overlays remain functional) and the console reports:
Uncaught abort(OOM), Build with -s ASSERTIONS=1 for more info with a code location that points to RecastJS.
To investigate, I started a scene and then, after loading and initial stabilization, I ran Chrome’s memory allocation timelines tool, which is designed to troubleshoot memory leaks by identifying objects that remain in memory without getting garbage collected for long periods of time.
The results show
Vec3 objects from recast.js are continuously allocated and remain in memory for at least 5 minutes.