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
Memory leaks in 2019.1.1.0
Moderator: juanjgon
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
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
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
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.
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D
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.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.
Thanks,
-Juanjo
On the master computer for sure, but it could be on both. Cant really remember.juanjgon wrote: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.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.
Thanks,
-Juanjo
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D