Earlier this morning, we linked to a Variety article detailing a mysterious issue knocking out Mac Pros across Hollywood.

Avid emailed us the following statement:

Avid is aware of the reboot issue affecting Apple Mac Pro devices running some Avid products, which arose late yesterday. This issue is top priority for our engineering and support teams, who have been working diligently to determine and resolve the root cause. As we learn more, we will immediately publish information—directly to our customers and via our community forums and social media platforms—in order to resolve this issue for all affected customers and prevent any further issues.

More as we hear it.

UPDATE: Avid shared a video with us this evening, with the latest updates on the situation.

UPDATE 2: Avid sent us this update this morning:

Today, Avid is confirming that the root cause for a reboot issue encountered by some of our customers has been identified and is unrelated to Avid and its creative tools. Google confirmed that a Chrome update “may have shipped with a bug that damages the file system on macOS machines.” Google has paused its release and provided instructions for affected users.

Avid is also pleased to share that it has received no reports of data loss by affected customers. From the beginning when this issue was made known to Avid, our teams actively worked with customers, Apple and partners to identify solutions and communicate them to customers. At this time, most affected Avid customers have recovered from this issue by reinstalling their macOS. Avid received no reports of incidents from customers running on non-Mac operating systems. To reiterate, this was not an Avid issue, as was reported in some early media coverage.

And from the Google Chrome support team:

We recently discovered that a Chrome update may have shipped with a bug that damages the file system on macOS machines with System Integrity Protection (SIP) disabled, including machines that do not support SIP. We’ve paused the release while we finalize a new update that addresses the problem.

If you have not taken steps to disable System Integrity Protection and your computer is on OS X 10.9 or later, this issue cannot affect you.

If this bug affected you, follow this link to the Google Chrome support article for details on the fix.