Memory leak/error

Sat Dec 03, 2016 10:38 pm

I will keep an eye and if it crashes again and I will send you as much info as I can gather.

Thanks again!

Sun Dec 04, 2016 12:07 am

Is Octane what crashes, I don't think is because of the textures,.

In the previous version I was using even heavier textures (8k maps for all pieces of the model) and never crashed, it was just the memory problem.

Checked in R16 and R17 as well, same result, it crashes randomly on both LV and PV.

Attached bugreport form cinema and a secreenshot of the message on screen

Sun Dec 04, 2016 7:34 pm

Interesting! I catched crashes with latest test SDK too. Here is another build with previous SDK(3.04.5). Would be great yo hear some feedback for this! Thanks for you helps!
https://render.otoy.com/customerdownloa ... -test1.zip

Sun Dec 04, 2016 9:05 pm

Thanks Aoktar!

Running a render right now.
I will try this new build and run some tests later tonight!
I will send you more info as soon as I have it.

Wed Dec 07, 2016 7:47 pm

Hi Aoktar!

Run some test and 2 big renders, same scene, different camera angles one with 4k textures and one 8k textures and open Sub-d modifiers to load the project with more weight.

No crashes, stable at 16G of ram in the heavier project the whole way through.
Both shots had 600 frames

So it seems that is safe to say that this build is stable .

I noticed however that in certain instances after closing cinema the memory is not released and cinema 4d remains visible in the task manager of Windows 10, I am not sure if this is a problem of Octane or Cinema4D.
It happens in all 3 versions. It is not too much of hassle as ending the task solves the issue. But may be is worth taking a look?

Aside from that works like a charm.

Going to test with image sequences as texture today. If anything happens I will let you know.

THANKS SO MUCH FOR THE HELP!

Wed Dec 07, 2016 7:55 pm

Roboto wrote:I noticed however that in certain instances after closing cinema the memory is not released and cinema 4d remains visible in the task manager of Windows 10, I am not sure if this is a problem of Octane or Cinema4D.
It happens in all 3 versions. It is not too much of hassle as ending the task solves the issue. But may be is worth taking a look?

Great to hear!
About other question, i'm aware of that and lookings for reason. Do you have activated "Allow to send renderstats to Otoy"? It may be worth to disable and try again.