-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maximum call stack size exceeded #350
Comments
It was added in pex-context@3 alpha to avoid |
Easiest way ATM to recreate issue it to create lineMaterial const cubeEntity = createEntity({
transform: components.transform(),
geometry: components.geometry(cube()),
material: components.material({ type: "line" }),
});
world.add(cubeEntity); That will crash lineRendererSystem at |
We should try/catch renderEngine.update/render in ctx.frame and return false on error to stop the loop. Restarting the raf will need better devx than a reload in Nodes. |
- avoid this.drawMeshes.bind(this) which causes Maximum call stack size exceeded everywhere but Chrome Closes #350
Happens when pipeline crash. Looks like RAF stacks to infinity on error
Can this be caused by
requestAnimationFrame(frame.bind(this));
in pex-renderer?The text was updated successfully, but these errors were encountered: