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
The longer the viewer runs, the more RAM it uses and the slower it renders. To reproduce this issue, create a loop that changes a small scene repeatedly and call view_all() in each iteration. The performance will degrade over time and RAM will increase indefinitely. In my test, rendering this animation for 3 minutes increased the RAM usage to 7GB.
out.mp4
The text was updated successfully, but these errors were encountered:
This behavior is the same in VSCode or standalone and exists in the viewer server (although I have not explicitly checked if this problem exists on the CAD script side as in my case this typically becomes and issue over multiple runs rather than a single long run)
How do you create this loop?
Do you use the animation feature?
Or simply draw "frame after frame" and screenshot it.
I don't really know how javascripts garbage collector works or how I can profile a web app in the browser. Need to find out to see whether the issue is on my code (most probably) or in threejs (the only dependency of the viewer)
Also, you may notice that the object flashes which is caused by the lighting changing when first drawing the object, then it is re-rendered with the correct lighting. The flashing is obviously a bug but it is also rendering the scene twice unnecessarily.
The longer the viewer runs, the more RAM it uses and the slower it renders. To reproduce this issue, create a loop that changes a small scene repeatedly and call view_all() in each iteration. The performance will degrade over time and RAM will increase indefinitely. In my test, rendering this animation for 3 minutes increased the RAM usage to 7GB.
out.mp4
The text was updated successfully, but these errors were encountered: