You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
frontend/js/library-3d.js: Large 3D models loading synchronously, blocking the main thread #425
I have gone through the issue and understand the problem.
Problem Summary:
The file frontend/js/library-3d.js is loading large 3D models synchronously, which blocks the main thread and causes UI freezing or lag, especially on slower devices.
Proposed Solution:
I will refactor the model loading flow to make it asynchronous so that it does not block the main thread.
Planned improvements:
Move heavy 3D model loading to async flow
Use non-blocking loading techniques (async/await or lazy loading where applicable)
Add a loading spinner/progress indicator during model load
Explore Web Workers if any computation-heavy tasks are involved
Ensure smooth rendering without freezing UI
Expected Outcome:
No UI blocking during model load
Improved performance and responsiveness
Better user experience on low-end devices
If the issue is still open for contribution, I would like to work on it under GSSoC'26. Kindly let me know if I can take this up.
Activity
Dhrupad-05 commentedon May 10, 2026
Hi @devanshi14malhotra, I’d like to work on this issue under GSSoC’26.
Proposed Solution
I’ll refactor the synchronous 3D asset loading flow in
frontend/js/library-3d.jsto use asynchronous loading mechanisms for large models.The implementation may include:
Expected Outcome
Please assign this issue to me.
RAGASUDHA-B commentedon May 17, 2026
Hi @devanshi14malhotra,
I have gone through the issue and understand the problem.
Problem Summary:
The file frontend/js/library-3d.js is loading large 3D models synchronously, which blocks the main thread and causes UI freezing or lag, especially on slower devices.
Proposed Solution:
I will refactor the model loading flow to make it asynchronous so that it does not block the main thread.
Planned improvements:
Expected Outcome:
If the issue is still open for contribution, I would like to work on it under GSSoC'26. Kindly let me know if I can take this up.