Memory leak, v2 scene -> v3(SOLVED)

Sub forum for bug reports

Moderators: ChrisHekman, aoktar

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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).


Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Post Reply
ratata
Licensed Customer
Posts: 74
Joined: Tue Aug 19, 2014 1:28 am
Location: Ljubljana, Slovenia
Contact:

Hello,

came upon a case of a memory leak, I opened an v2 scene in v3 and it was gobbling up the RAM until cinema goes out of memory when you hit the render.

On investigation (deleting everything not related to leak) it came down to a combination of Octane Camera Tag and a specific object in the scene, by deleting either of them the problem goes away.

This is of course simply solved by deleting the tag and creating it again in v3, but I guess it still worth reporting since it is not normal behavior.

Octane log gives nothing special just export info, no crash report since it hard crashes - out of memory windows popup.
Krka_oct3_remake_33_leak_0005.zip
(1.18 MiB) Downloaded 243 times
If I render this scene in Live viewer the ram looks like this:
oct3_memoryLeak_01.JPG
And it keeps rising until the crash. And if I delete Oct camera tag, it works fine, or if I delete the Loft mesh, it works fine, only if both are present this happens.

C4D R17, Oct 3.00-R1, Win 10

Cheers,

Sandi
http://www.twitter.com/sandidolsak

6850k|64gb|4 x GTX980ti
User avatar
aoktar
Octane Plugin Developer
Posts: 16066
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

thanks
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
ratata
Licensed Customer
Posts: 74
Joined: Tue Aug 19, 2014 1:28 am
Location: Ljubljana, Slovenia
Contact:

Hey aoktar,

some update on this matter, it looks like the problem is I was going back and forth between v2 and v3 with the scene, and I was using a camera tag in v2 that was set to baking in v3, but since v2 has no baking it worked like thinlens, and now when I opened it back in new v3 it recognized baking setting again...

So I guess my machine doesn't have enough RAM to process this...
http://www.twitter.com/sandidolsak

6850k|64gb|4 x GTX980ti
User avatar
aoktar
Octane Plugin Developer
Posts: 16066
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

I can't see the problem as you said about memory leak. Do you render one frame?
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
ratata
Licensed Customer
Posts: 74
Joined: Tue Aug 19, 2014 1:28 am
Location: Ljubljana, Slovenia
Contact:

I was rendering just to Live Viewer, I noticed that if I close all other apps, it actually does start redering eventually, but it does eat up alot of RAM before it start then it drops down, but interestingly it doesn't do that if I delete and create a new tag.

So I don't know, I guess the tag got corrupted at some point...
http://www.twitter.com/sandidolsak

6850k|64gb|4 x GTX980ti
User avatar
aoktar
Octane Plugin Developer
Posts: 16066
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

ratata wrote:I was rendering just to Live Viewer, I noticed that if I close all other apps, it actually does start redering eventually, but it does eat up alot of RAM before it start then it drops down, but interestingly it doesn't do that if I delete and create a new tag.

So I don't know, I guess the tag got corrupted at some point...
Tag does nothing itself on memory/rendering. Octane makes renders. I think "bake camera" is eating much ram and calculation is going hard.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
ratata
Licensed Customer
Posts: 74
Joined: Tue Aug 19, 2014 1:28 am
Location: Ljubljana, Slovenia
Contact:

Yep you are right, so the fault for the RAM build up is actually a bad UV map, issue solved, thanks for looking it up.
http://www.twitter.com/sandidolsak

6850k|64gb|4 x GTX980ti
Post Reply

Return to “Bug Reports”