Crashing A Lot when IR Is Open

[BigAl3D]

I'm getting a lot of crashes in Beta1 and Beta2 daily May 30 2018 (core 2 DailyBuild May 30 2018) if I have the IR open. It works generally, but if I start scaling something, moving something or adjusting parameters of an object, boom. Crash. I've attached the crash report, but it seems to point to the Embree engine as the "trigger." How is Corona and Embree linked at all?

[houska]

Corona uses Embree as the raytracing kernel to be able to resolve casting of a ray into the scene as fast as possible.

Regarding your issues, do you have some specific circumstances in which the crashes are reproducible? For example, does it happen only in one specific scene or when you are working with one specific type of an object? The thing is that apparently the IR works fine for most of the users, so there must be something that you are doing differently that's causing the crashes. If we find what it is, we'll be able to fix the issue.

[houska]

Actually, looking at your bug report, in this case it's C4D calling embree from the shader evaluation. They're using Embree probably for the same reason as Corona - to be able to shoot rays into the scene in a fast and effective manner. Based on that, I'd guess the shader that it was crashing on was something like C4D's AO shader

[BigAl3D]

Yeah nothing too specific. The only real consistent thing is when the the VFB window is open and it's set to IR. I just reviewed all the materials in my scene and I found one material that contained a C4D AO shader. It is a material I got from a scene file provided in my other thread (https://forum.corona-renderer.com/index.php?topic=20399.msg127222#msg127222). It's the car tire material in the Diffuse tab. I just deleted it so I will see my scene still crashes.

Thanks.

[BigAl3D]

Some more info on this. After deleting that AO Shader, I had almost no crashes except when I did one thing... rotate one of the objects. I could move them, but if I rotated them, Corona would begin to recalculate, but before it finished pass one, crash. Only rotating an object. One new thing is I just got this warning, but no crash:

System is running low on RAM. You may experience excessive parsing times and/or crashes. You will probably have to simplify the scene.

4 GiB of physical RAM used by Cinema 4D
8 GiB of virtualized* RAM used by Cinema 4D
33.1 GiB of virtualized* RAM used by all running applications
32 GiB of physical RAM installed on system
47 GiB of virtualized* RAM provided by OS

* virtualized RAM means physical RAM + swap file on HDD/SSD

Corona RAM usage breakdown:
  71.2 MiB beauty/multi-pass

Are there any setting I could change for better RAM optimization?

[houska]

You say it was crashing after rotating an object. What I didn't understand is whether it was happening for any object or only for one specific object in the scene? If it was only one specific object, could you share it with us somehow - maybe through a scene with just the single object (after making sure that it still crashes in the new scene)?

Regarding the RAM - there's really no other general option than simplifying your scene. Also, try to use render instances where possible. And reduce the number of multipass passes. But looking at the report, it seems like C4D (with Corona and everything) only uses 8GB of RAM? That's not so huge to be honest...