vray hangs for 3-4 mins after rendering a frame

[pixeldrone]

Hello, I have a scene that when I render it takes about 3-4 mins, no problem. However after it appears to be completed on render it hangs for another 3-4 minutes until I can use max again.
When I turned the log onto verbose, I could see that it was loading HDRI maps (VRaybitmaps) during this 3 minute lag period. not every seen with this same asset responds this way as well so I am not
totally sure why it is doing this.
I monitored network activity during this time and there is very negligible traffic however the CPU is pretty maxed out during this time period. I did notice that it does this same procedure when I am navigating
through the material editor as well and it causes the material to lag for 3-4 minutes as well when I click on a bitmap node etc.

Does anyone know what might cause this and what I might do to fix it?

Thank you.

best, Christian

[^Lele^]

It' likely to be memory release.
Do you have foliage/proxies/dynamic geo in abundance?

[pixeldrone]

as a matter of fact I do. The scene is kind of a running track stadium and the modules of the stadium have been written out to VRay Proxies and the main character in the scene is an alembic import with many external textures linked to the character. Do you have any suggestions on how to release the memory or recommended settings that I need to pay attention to?

Best, Christian

[^Lele^]

Not much you can do locally, besides task-manager-quitting Max.
If you're rendering with Deadline (i name this one as i know of the option it has, for sure. others may provide it too.) you can try and turn on the restart of the renderer between frames, which should quit max and start a new session, hopefully quicker than waiting.
We have changes to this in the pipeline, but they aren't trivial at all, so they have been taking a while longer than expected.

[Vizioen]

Not much you can do locally, besides task-manager-quitting Max.
If you're rendering with Deadline (i name this one as i know of the option it has, for sure. others may provide it too.) you can try and turn on the restart of the renderer between frames, which should quit max and start a new session, hopefully quicker than waiting.
We have changes to this in the pipeline, but they aren't trivial at all, so they have been taking a while longer than expected.

Does that mean this issue might be solved in the future? Oh god please yes. Quick memory release would be awesome.