Hi Juan,
I'm doing a long sequence (600ish frames), and need to do a full scene update on each frame due to large-ish alembic files with changing topology. Still frames works wonders, it usually peaks around 4-5 gb in memory usage.
Now I've noticed it doesn't max out my TitanX card (12gb ram) but my on board memory just keeps expanding and expanding. Until its used all 24 gb of memory and then crashes. Which right now means I have to babysit my renders.
I've not had this problem with Mantra before, but then again I am testing out a new lighting pipeline so who knows.
Perhaps we need to look at flushing the memory both in terms of on board and GPU memory between frames ?
Is this something you've experienced ?
Memory leak ?
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)
I'd love to send you a scene, but I'm NDA'd up to my ears. Besides, alembic caches are clocking in at 15gb each.
If it matters, I've got one big alembic cache at 15gb, (about 400mb a frame) and 5 instanced verisions dottet around, so I dont know if this is an instancing issue. Oh and two 8k textures.
It all renders fine and each frame clocks in about 5gb each, so Octane have no problems rendering the sequence, it just seems to accumulate over the range. And then it crashes when it reaches my 24gb system memory. But not always, I jsut had once instance where it just shut Octane and Houdini's rendering down but not Houdini itself.
But it looks like its not clearing the system cache between frames, perhaps just a checkbox in the rop to do this would be good ?
If it matters, I've got one big alembic cache at 15gb, (about 400mb a frame) and 5 instanced verisions dottet around, so I dont know if this is an instancing issue. Oh and two 8k textures.
It all renders fine and each frame clocks in about 5gb each, so Octane have no problems rendering the sequence, it just seems to accumulate over the range. And then it crashes when it reaches my 24gb system memory. But not always, I jsut had once instance where it just shut Octane and Houdini's rendering down but not Houdini itself.
But it looks like its not clearing the system cache between frames, perhaps just a checkbox in the rop to do this would be good ?