thatopen-errors-performance

Memory leaks in ThatOpen BIM viewers occur when large models are loaded and unloaded repeatedly without proper disposal calls, causing GPU memory retention. Enforcing a strict disposal discipline and per-model cleanup order prevents undisposed resources and tab crashes.

Diagnose high GPU usage and slow rendering by applying memory monitoring patterns to identify undisposed resources and performance bottlenecks. Offloading heavy operations to Web Workers keeps the main thread responsive and stabilizes rendering.

The best way to handle repeated load and unload cycles is by enforcing explicit disposal calls and per-model cleanup to avoid GPU memory retention. Memory budgeting and profiling guidelines ensure stable performance during long-running sessions.

Yes, Web Workers are required to offload heavy operations from the main thread, keeping the UI responsive. A proper worker setup combined with memory monitoring patterns prevents UI freezes during large-model rendering.

Fix undisposed resources by applying an explicit teardown order and per-model cleanup to prevent GPU memory retention. Combine disposal discipline with worker offloading and memory budgeting to eliminate performance bottlenecks.