OTOY Forums

Since the latest version of Octane i've been running into problems with system memory.
Im on a Mac Pro 2012 24 gb ram. 4x gtx780tis. 10.11.5 c4d r18

If i leave a scene rendering over night that has a lot of multiple layers going on and a good number of frames, the whole system eventually runs out of ram and i get an OS message saying.
"Your system has run out of application memory” and all my apps get paused including c4d. I have plenty of free space on the hard drives but it seams it must be filling up the RAM and not being able to empty it.

I might be wrong about what is causing this problem but it seems directly linked to c4d/octane renders. Is it possible a memory leak or something cumulative?

Any advice as to a fix or what might be causing the issue would be great.

Hi,
I don't suppose there's a big mem-leak possibility. I didn't changed any codes to cause this. Can you note that how and where occurs? I'd be happy to see if you have a scene to reproduce.

Hi Aoktar.

This is happening to me as well on windows 10
I run i7, 64g of Ram and 3 Titan X Maxwell

It keeps adding Ram every time starts a new frame.
Started to happen since the last update and I have rendered heavier scenes than this one before

Tried in R16, R17 and R18, same result.
If I disable the "out of core" function it somewhat takes longer to fill up the memory but eventually I get the message.

https://drive.google.com/file/d/0BwjXgz ... sp=sharing

attached my scene file.
any ideas?

I have found something very strange while testing user scenes. Ram usage was significantly increasing on evert frames. Somehow notified that when i select an octane material then ram usage started to be constant. Im not still sure but in materials maybe a bug. I'm still invistegating.

Thanks for the quick response Aoktar!

Please keep us posted!

Roboto wrote:Thanks for the quick response Aoktar!

Please keep us posted!

Are you sure that's happening with R16/17? I just found something is about R18.

In my case it happens worse in R16 and R18

I found that i suppose. It was something with ImageTexture in mix materials. ImageTexture was not deleting the allocated image data in animation renderings.

Here is a test build with 3.05-test sdk:
https://render.otoy.com/customerdownloa ... t1-win.zip

Hi Aoktar!

Been rendering since 9:00 AM PST the scene attached.
almost 2 million polygons with over 5 gigabytes of textures.

So far has remained stable at 15gigabytes of ram the whole way through.

Before starting the render it crashed 2 times on the LV and the first time that I sent the scene to render to the picture viewer, but I assume this is because this version is a test build.


I will keep you updated if any issues arise during the weekend.

So far is rendering like a champ, Thanks a lot Aoktar!

Roboto wrote:So far has remained stable at 15gigabytes of ram the whole way through.

Yes. This points to a success.

Before starting the render it crashed 2 times on the LV and the first time that I sent the scene to render to the picture viewer, but I assume this is because this version is a test build.

I don't think it's about being test version. But i'm not completely sure. This can be about lot of textures. Do you have any info about crash? What's that? C4D crash or cuda errors?