Skip to content

[BUG]: Engine hangs awaiting getItemsByVisibility #705

@ShaMan123

Description

@ShaMan123

Describe the bug 📝

Related #699

Using model#getItemsByVisibility with large models causes the engine to hang.
Is this related to Set usage of very large datasets? Just a guess.

I sent @agviegas the IFC that causes this to happen. It does not happen with /resources/frags/school_arq.frag

Reproduction ▶️

https://stackblitz.com/edit/vitejs-vite-efp6fmgp?file=src%2FViewer.ts

Steps to reproduce 🔢

  1. Open repro
  2. Upload frag file containing large model
  3. Open console
  4. Logs of visual items should appear - if engine hangs they do not

This has no affect on the canvas

System Info 💻

System:
    OS: macOS 26.3
    CPU: (12) arm64 Apple M2 Max
    Memory: 1.22 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.12.0 - /Users/shaman123/.nvm/versions/node/v24.12.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 11.6.2 - /Users/shaman123/.nvm/versions/node/v24.12.0/bin/npm
  Browsers:
    Chrome: 145.0.7632.117
    Safari: 26.3

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

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 repository 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 Community.
  • The provided reproduction is a minimal reproducible example of the bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions