corona image Version: B1 (core 1.7) crash everytime on OS X yosemite

[Nikola]

Thank you for the screenshots, these problems are really strange, especially the first one. I uploaded a new testing build, please download the build again (from the same URL) and install it again and then click "Crash App" for both cases and send me the BugReport.txt for both cases.

Thank you
Nikola

[ASIMO]

Hello Nikola

I uploaded the two bugreports to your server. They are marked with _1 or _2 in the filenames. The first one is the report showing up while starting Cinema4D. The second one refers to the one showing up during the render process.

1522402364_asimo-bugreports.zip
_

Hopefully this is helpful. Thank you

best. Asimo

[Beanzvision]

I had no issue with this scene also.

[ASIMO]

Hello beanzvision

So it rendered all passes till finish ?

Do you think it might have to do something with my MacOS system ? Which version are you working on ?

I will try to update it to the newest version and then run a new test.

best

Asimo

[Beanzvision]

I only ran 50 passes which took some time, let it denoise then saved the cxr. I'm a Windows user so I can't say whether it's OS related or not. It may even be the fact that AO is activated in the render settings but that is just speculation. Have you tried rendering without AO activated?

[ASIMO]

Hello beanzvision

Thank you for your help and your time. The AO option really was activated. But it does not matter. I updated my system now to the newest configuration. macOS high Sierra but without any change. The file still does not work. I got the same crashes.

Has anybody else of you tried to render it on a Mac OS System ?
_

Thanks

Asimo

[Nikola]

Hi ASIMO,

I sent you a private message, did you receive it?

Nikola

[ASIMO]

Hi all

Unfortunately I still got issues with that problem. Also the newest build does not solve it.

During the last months it never happened again and I could finish over 20 projects. But now it appears again.

I have to stay Corona is amazingly stable most of the time and I am talking about 1 % of my renders. Still it matters.
_

For what I can say it has nothing to do with the general setup, with used textures, materials or tags. I do not even believe that the 3D Models used are causing it.

Since I built up models externally and import them with a plugin, maybe this is causing the error from time to time ?
_

Also the error seems to happen differently on different machines, so I would say it may be hardware bound ?
_

I would really appreciate your help to figure out at least what part (File / Software / Hardware / Plugin) is the origin of the problem.

So that I can try to figure out a workaround for avoiding it.
_

 Thank you so much for your support !

[ASIMO]

Hi

Attached there is a new bug-report with the newest build from 18 09 2018 using the provided scene I sent to you.

Thank you for any help / advice.

[HFPatzi]

Hi,

one reason could be the mac osx lock screen. The one you can disable in the osx security settings.
I my case my main machine (windows) crashed because one of the render clients (osx sierra) went into the lock screen.
Maybe you try to uncheck the checkbox marked im my screenshot (unfortunatly it's german).
I know this is an older topic, but maybe this helps.

Greetings,
Patzi

[ASIMO]

Hello HFPatzi

Thanks for the tip with the lock screen. Basically it has never been an issue but who knows. I will keep it unlocked for the next renders to see if it makes a difference. What I did anyway is to block the MacOS Sleeping Mode for the hard-drive. This really forced my C4D to stop working until I logged in again.

I speak german so I could read everything. Danke !

Greetings
–A

[Beanzvision]

I hope you guys plan on updating to B2 ;)