Viewport3DX has memory leaks

[SuperYF-86]

Multiple Viewport3DXs sharing a single EffectsManager can improve loading speed, but it can also lead to memory leaks. I'm not sure if this is a bug or if I haven't found the right way to dispose the Viewport3DX?

Some resources never seem to get cleaned up when sharing EffectsManager.

This is the demo project：
ViewportMemoryLeakTest.zip

[holance]

Yes, there are some internal caches for things like shaders etc. So as long as the memory is not keeping increment each time you load an new scene, it should be ok.

[SuperYF-86]

Yes, there are some internal caches for things like shaders etc. So as long as the memory is not keeping increment each time you load an new scene, it should be ok.

I add a PointNode for each Viewport3DX.

<hx:Element3DPresenter Content="{Binding Root }" />

It is indeed not possible to release resources correctly when Viewport3DX shares the EffectsManager.

demo:
ViewportMemoryLeakTest.zip

[holance]

I don't see there is any memory leaks. For your tests, you didn't dispose the effects manager after closing all the windows. Like I said, effects manager creates a set of cache automatically to improve performance. It is not memory leak.

Here is the memory usage for the shared effects manager:

You can see every time you create and close all windows, memory went back to the same level. Of course, it won't be back to the level at the beginning because of the caching. You can dispose the effects manager if you really need to release all resources.

[SuperYF-86]

I don't see there is any memory leaks. For your tests, you didn't dispose the effects manager after closing all the windows. Like I said, effects manager creates a set of cache automatically to improve performance. It is not memory leak.

Here is the memory usage for the shared effects manager: You can see every time you create and close all windows, memory went back to the same level. Of course, it won't be back to the level at the beginning because of the caching. You can dispose the effects manager if you really need to release all resources.

You're right, it shouldn't be a memory leak. Because memory usage doesn't increase indefinitely.

Viewport3DX seems to follow some kind of lazy pattern. It doesn't actively update unless the rendering interface has changed.

I have observed that when a Viewport3DX Camera has changed, some resources are being freed up quickly.

I guess when I need to actively release resources, I need to make sure that at least one active Viewport3DX exists in the current project, or create a new one. Trigger its internal resource release mechanism by updating its rendering state.

I don't know if this approach is officially recommended, but at least it works for my project.

Anyway thanks for your reply, it helps me a lot.

[holance]

You need to force gc multiple times to release resources, there's nothing to do with viewport.