thatopen-errors-performance

Browser crashes and UI freezes in ThatOpen viewers are typically caused by memory leaks from undisposed Three.js GPU resources, missing worker initialization, and blocking main-thread operations during large IFC model loading.

To dispose of Three.js resources in ThatOpen, use `components.dispose()` for full teardown and `fragments.disposeModel(modelId)` for per-model unloading, ensuring geometries, materials, textures, and render targets are explicitly destroyed to prevent GPU memory leaks.

To stop main-thread blocking during raycasting or data queries, initialize `FragmentsManager` with a correct version-matched worker URL to offload heavy operations, keeping the UI responsive under heavy GPU usage.

The best way to optimize ThatOpen performance for repeated workflows is to load fragments instead of raw IFC repeatedly, apply IFC class filtering, and use model federation to manage memory safely across load and unload cycles.

To fix z-fighting in ThatOpen BIM overlays and highlighting, apply polygon offset techniques to resolve depth buffer conflicts, ensuring stable rendering performance under heavy GPU usage.

Yes, you can use ThatOpen components for large model optimization without memory leaks by following correct disposal ordering, explicitly cleaning up Three.js GPU resources, and using DevTools memory profiling to diagnose leaks across load and unload cycles.