Maximum call stack size exceeded

[MiguelG97]

Describe the bug 📝

when initializing the components from the boilerplate code I receive a Maximum call stack size exceeded RangeError:

I'm using the boilerplater :

// Initialize the basic components
const container = document.getElementById("container");
const components = new Components();
//console.log(components);
components.scene = new SimpleScene(components);
components.renderer = new SimpleRenderer(components, container);
components.camera = new SimpleCamera(components);
components.raycaster = new SimpleRaycaster(components);
components.init();

// Add some elements to the scene
const scene = components.scene.get();

const geometry = new BoxGeometry(3, 3, 3);
const material = MeshStandardMaterial({ color: "red" });

const cube = new Mesh(geometry, material);
cube.position.set(0, 1.5, 0);
scene.add(cube);

components.meshes.push(cube);

Dependencies

Reproduction ▶️

No response

Steps to reproduce 🔢

Type the boilerplate
execute the init() command from the component class

System Info 💻

--sytem

Used Package Manager 📦

npm

Error Trace/Logs 📃

Uncaught RangeError: Maximum call stack size exceede

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a IFC.js components issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[agviegas]

Hey, can you provide a minimal app where we can reproduce it? What browser are you using?

[MiguelG97]

Hi anton! It was deployed on google chrome. Sure I will provide one sooner

[sjovanovic]

I encountered this error a lot when parsing ifc files. (I just call ifcapi.StreamAllMeshes(modelID, (flatMesh)=>{ }) )
In Nodejs if I increase the stack with --stack-size option it works.
But on some of the files when I increase the stack the error just changes to "Segmentation fault: 11"

[agviegas]

I'm closing this for now as we couldn't reproduce this. Let us know if this keeps happening with the latest version and you can provide a way for us to reproduce it!

[vulevukusej]

@agviegas I have a file which causes this issue as well, and the error occurs when using https://platform.thatopen.com/app as well. Can I share the file privately?

[agviegas]

Hey @vulevukusej yes, please! Please open an issue in web-ifc and share the model with antonio@thatopen.com. Cheers!