V-Ray 5 - Crashes on Mac Pro when using all 28 cores

[deyan.hadzhiev]

Hi klex167, the second number is good, but the first one is troublesome and most probably is one of the reasons for the crash. Even if you did a complete new install, this seems to be the default system limit for MacOS, so I think it would have had the same value in the past, if you did not change it explicitly.
The reason the thread count has effect on this, is because that limit is more easily reached the more threads are used.
We will try to improve our implementation to avoid passing that limit in the future, but until we manage to make the change, the only workaround would be to change the system limit to a higher value.

[OhGott]

Hi deyan.hadzhiev , thanks for the explanation.
I will try to increase the value, if I find a way to do so and will test V-Ray 5 again when I have more time.

Thanks again for your response to my initial request.

Regards

[deyan.hadzhiev]

Just for testing this, you can try executing this in a terminal (it will set the limit to 8192, which should be more than enough):

sudo launchctl limit maxfiles 8192 200000

Note that this setting will not be persistent and will last only for the current session. Making this persistent between restarts is more complex, but doable.

[OhGott]

Hi deyan.hadzhiev thanks for the support. Very helpful.
I will try this when I have more time.

Regards.

[sirio76]

Really hope you'll have time to test this and that Deyan solution will work, this is the only reason why I'm still waiting to purchase a new CPU

[OhGott]

Hi sirio76 , I'm also very interested about this.
I hope to find a slot in the next few days.
I'll keep you updated.

[sirio76]

Thanks a lot

[michael_olssson]

I don't really know what I'm doing here but this is how it looks now:

[deyan.hadzhiev]

The ulimit command is a shell builtin and it does not seem to update properly. Proper way to check that the changes are applied is just calling the limit part without arguments:

# This checks the current limits for the user
launchctl limit maxfiles

# This changes the current limits for the user
sudo launchctl limit maxfiles 8192 20000

Just to note again that calling this in a terminal changes the limits only for the current session - restart of the machine will reset this limit. This is only for testing.
In the meantime we are testing a potential fix/improvement on our thread usage, that should fix this problem.

[sirio76]

Thanks Deyan, please keep us updated!

[OhGott]

Hi sirio76
deyan.hadzhiev

I did a quick test on a fresh C4D / V-Ray 5 Hotfix 1 install.
I used the same scene as before, where I had crashes.

IPR with unlimited threads cause no issues at all!

I have currently no time for in depth testing but the issue I had seams to be gone.
I even havn't had to max the OS file limit.

Further testing will follow as soon I have more time.

Thanks.

[sirio76]

Hi sirio76
deyan.hadzhiev

I did a quick test on a fresh C4D / V-Ray 5 Hotfix 1 install.
I used the same scene as before, where I had crashes.

IPR with unlimited threads cause no issues at all!

I have currently no time for in depth testing but the issue I had seams to be gone.
I even havn't had to max the OS file limit.

Further testing will follow as soon I have more time.

Thanks.

Thanks lot for the test! I'll order the CPU next week! May I ask what OS version are you using?

[OhGott]

sirio76 I have Mac OS Catalina latest installed, since I don't know how Big Sure behaves.

[sirio76]

Ok thanks!