OTOY Forums

I am rendering a pretty simple scene with growing ivy and every 14-18 frames I need to restart Houdini because of "Not enough GPU memory" error (it renders last 3-4 frames incorrectly — with transparent ivy geomerty and then fails saying that "restart required")

Viewport screenshot: https://i.imgur.com/Aj53Qu8.png
Rendering Stats screenshot: https://i.imgur.com/47yHBzC.png

A. Windows 10
B. GeForce GTX 1660Ti 6Gb
C. 32 Gb RAM
D. Driver version 436.48, 10/01/2019
E. Octane Render Standalone 2019.1
F. 2019.1.1.0
G. Houdini Indie 17.5.360

Hi,

Sorry, this problem can be related to a memory leak that I'm investigating that happens while rendering sequences in full scene reload mode from the main Houdini GUI. I hope to know more about it soon, but meanwhile, the workaround is to render the scene frame by frame, perhaps using a script, hqueue or deadline. You are rendering in full scene reload mode, so the render times while rendering frame by frame should be near the same.

Thanks,
-Juanjo

Can you please send me this scene to use it as a unit test while evaluating the fix for this issue?

Thanks,
-Juanjo

Sent via PM.

Yes, I have to use the "Full reload" rendering method to make it render animation properly.

The new plugin build 2019.1.2.0 just released should have all these memory leaks while rendering in full scene reload mode fixed.

Thanks!
-Juanjo

Thank you! I'll give it a try!

Looks like everything works well! Thank you very much!

I think there are still memory leaks in 2019.1.2.0 when using network rendering. I had an issue where it render 100 out of 900 frames then crashes cause not enough memory. It works just fine when i disable network rendering.

galleon27 wrote:I think there are still memory leaks in 2019.1.2.0 when using network rendering. I had an issue where it render 100 out of 900 frames then crashes cause not enough memory. It works just fine when i disable network rendering.

Where do you have the crash, in the master computer or in the render nodes? This sounds like some kind of core issue because there is no code related to the network rendering on the plugin side.

Thanks,
-Juanjo

juanjgon wrote:

galleon27 wrote:I think there are still memory leaks in 2019.1.2.0 when using network rendering. I had an issue where it render 100 out of 900 frames then crashes cause not enough memory. It works just fine when i disable network rendering.

Where do you have the crash, in the master computer or in the render nodes? This sounds like some kind of core issue because there is no code related to the network rendering on the plugin side.

Thanks,
-Juanjo

On the master computer for sure, but it could be on both. Cant really remember.