-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Update vtk.js to prevent memory increasing #1411
Comments
My colleague on work constantly faces that problem. He's in anguish and pain. It would be great if this could be fixed as soon as possible! |
This is not about the garbage collection you're referring to. They recently added a new shared mapper (which we already have), and that is related to garbage collection. If you give me reproducible steps i can take a look at the memory leak |
Initial values: After some clicks on elements: I have changed your example with basic StackViewport and able to reproduce:
|
@sedghi Were you able to reproduce it? |
Haven't looked at it, but will upgrade vtk in near future since i'm pushing on cornerstone 2.0 |
What feature or change would you like to see made?
Since 30.10.0 version developers of vtk.js added garbage collection to shared graphics resources. But if I will update it to myself, I will get error in cornerstone vtkStreamingOpenGLVolumeMapper file. Could you update vtk.js?
The problem is infinite increasing memory space when I use
setStack
on the elements to replace images.Why should we prioritize this feature?
Without this update we have infinite increasing memory space when using
setStack
on the elements to replace images.The text was updated successfully, but these errors were encountered: