Networking rendering on Macs causes daemon & mouse issues.

[alextrimpe]

Issue:
A network render leads to users having their mouse stop registering clicks, as well as the daemon application script stop responding.

Our Setup:
6 Macs using Octane, all are Mac Pro towers with Nvidia GTX980ti cards.
All cards are up to date, and all cuda drivers are up to date as well. All are running same version of Mac OS.

Process leading up to the daemon and mouse failures:
1. One user starts an Octane network render with all of our daemon slaves turned on.
2. Whether or not we are using C4D or Octane at all, several minutes into the render, 2 or sometimes 3 users begin having mouse issues (wherein the mouse can move around, but the clicks do not register)
as well as having the terminal daemon application stop responding (if I go into Activity Monitor and look at the daemon script, it is red, meaning it is not responding)

Temporary solution is to force quit the terminal application, which bring the mouse back to life. However, this obviously will slow down my coworker's network render as he can no longer use my daemon.

We have tried moving from wireless bluetooth mice to wired mice. Doesn't fix it.

Thanks!
Alex

[abstrax]

Issue:
A network render leads to users having their mouse stop registering clicks, as well as the daemon application script stop responding.

Our Setup:
6 Macs using Octane, all are Mac Pro towers with Nvidia GTX980ti cards.
All cards are up to date, and all cuda drivers are up to date as well. All are running same version of Mac OS.

Process leading up to the daemon and mouse failures:
1. One user starts an Octane network render with all of our daemon slaves turned on.
2. Whether or not we are using C4D or Octane at all, several minutes into the render, 2 or sometimes 3 users begin having mouse issues (wherein the mouse can move around, but the clicks do not register)
as well as having the terminal daemon application stop responding (if I go into Activity Monitor and look at the daemon script, it is red, meaning it is not responding)

Temporary solution is to force quit the terminal application, which bring the mouse back to life. However, this obviously will slow down my coworker's network render as he can no longer use my daemon.

We have tried moving from wireless bluetooth mice to wired mice. Doesn't fix it.

Thanks!
Alex

Could you check the memory usage? Is it possible that your system starts swapping because it runs out of memory?