Memoty Leak C4dtoa OIDN

[JHåland]

Hi, I have had a lot of crashing the last couple of days with 4.0.0.2. It uses all my memory 64 GB, rendering a simple scene, and I'm using the new noise reduction OIDN.

Got this message in the console: [imager_denoiser_oidn] /_display_driver_/Arnold_Intel_OIDN_denoiser: driver_process_bucket OIDN driver_process_bucket Filter Execute Error=out of memory

[thiago.ize]

Can you provide a complete arnold log with the most detailed verbosity level? It might tell us what is going on.

https://docs.arnoldrenderer.com/display/A5AFCUG/Log

[JHåland]

From the latest test I got this message: https://www.dropbox.com/s/vipnjewabi37zdp/console%20message%2013%2011%202021.rtf?dl=0

Where is the log file located? didn't know arnold had that

[JHåland]

Hi, I've tried to get more info with loging, but havn't gotten any more usefu info. I can render about 500 frames or so, and then it stops.

[Stephen.Blair]

The log file will be in the CINEMA 4D console, and in a file (if you enable File logging).

The log will have some stats for GPU memory usage (and CPU memory too).

We have a lot of experience reading log files, so we may get more out of it than you.

[JHåland]

yes, I though I had done everything correctly but hadn't changed it from warnings to info. so I'll try again. it will take some time, since I have to go through a lot of frames to get it to crash.

[JHåland]

here is the latest bug repport from c4d: https://www.dropbox.com/s/ooe1jqep7ldjeyf/_BugReport.txt?dl=0

[JHåland]

Here the log file with info;https://www.dropbox.com/s/gnvqf9aao18uyb6/arnold.0423.log?dl=0

[thiago.ize]

Thanks, but we still need the complete log with info level verbosity so that we can see what's happening.

[JHåland]

Hmm. Not really sure what you mean. All the other log files are empty. I can try to use the debug mode if that has anything more info.

[JHåland]

Ok I'll try again, now I've set it to be debug mode and here's all the log files to the crash: https://www.dropbox.com/s/8r0y6ujsdhoevke/log.zip?dl=0

[JHåland]

ok, now I had a crash without using OIDN, and by trying to zip this file my computer got a memory panic, blacking out my screens. So I'll can check if there's anything wrong with my memory cards. Here's the latest log: https://www.dropbox.com/s/ej55qdphp8l2cxe/log%202.zip?dl=0

[JHåland]

memory test says there's no error

[peter.horvath6V6K3]

Thanks Jørgen, I can reproduce the issue, we are looking into it.

[JHåland]

Thank you. I just updated to 4.0.1 and sadly the problem still occurs. Here's the lates log: https://www.dropbox.com/s/slenuqmdtvd1w8d/log%2024%2011%202021.zip?dl=0

I've tested a lot of possiblities for where the problem can be located. But I cannot find any solution that solve this.

[thiago.ize]

We didn't have time to fix this in 7.0.0.1. When this high priority bug is fixed, you should see ARNOLD-11852 listed in the release notes.

[JHåland]

Ok ,thanks. contact me if you need the scene file. No NDA on this project so that's no problem.

[thiago.ize]

Thanks for the scene offer! But this time around thankfully we already have a reproducible scene and already know what line of code is leaking the memory.

[JHåland]

aha! that's great. is there any tip for me to get it to render like normal?

[thiago.ize]

Aside from disabling imagers, I'm not yet sure of any easy workarounds.