Mac Screen Blacks Out and Freezes While Using Chrome After Updating to macOS 27.2

Since the problem started immediately after updating to macOS Golden Gate 27.2 and has occurred for three consecutive days, it may be related to a software compatibility issue, graphics rendering, or excessive system resource consumption.

A black or frozen screen while switching between Chrome tabs could potentially be caused by hardware acceleration, runaway background processes, excessive CPU or memory usage, browser extensions, or macOS graphics-related issues.

I recommend first disabling Chrome's hardware acceleration. Open Chrome, navigate to Settings > System, turn off Use graphics acceleration when available, and click Relaunch. This will help determine whether the issue involves Chrome's interaction with the Mac's GPU.

Next, open Activity Monitor (Finder > Applications > Utilities) and check the CPU and Memory tabs. Look for processes consuming unusually high resources, particularly Chrome Helper processes and background applications. Also check the Memory Pressure graph for yellow or red indicators and monitor swap memory usage. Runaway processes or memory leaks can contribute to system instability and application freezes. Apple's documentation explains how to monitor CPU activity, view memory usage, and identify running processes.

Make sure Chrome is updated, and temporarily disable browser extensions by visiting chrome://extensions/ to determine whether any extension is contributing to the problem.

It would also be useful to test Safari with a similar number of tabs open. If Safari works normally, the issue may be specific to Chrome. If other applications experience similar freezes, the problem may involve macOS, graphics processing, or hardware.

If the issue persists, check the Console application (Finder > Applications > Utilities) for recurring errors involving WindowServer, GPU, Chrome Helper, or memory-related processes around the time the screen freezes. Apple's guide explains how to view and search log messages in Console.

You could also start your Mac in Safe Mode to determine whether third-party applications or background services are contributing to the problem. Apple provides instructions for starting a Mac in Safe Mode.

Finally, check System Settings > General > Software Update for any newer macOS updates or supplemental fixes. See Apple's instructions on updating macOS.

To help identify the underlying cause, could you clarify the following?

1. What is your MacBook model and year, and is it an Intel or Apple silicon Mac?
2. Does the entire system freeze, or does only the display turn black?
3. Does closing and reopening the MacBook lid restore the display, or is a forced restart necessary?
4. Does the problem occur exclusively in Chrome or in other applications as well?
5. Have you noticed unusually high CPU or memory usage in Activity Monitor?
6. Have you tried disabling Chrome's hardware acceleration?

Since the issue appeared after the macOS update, I would initially investigate Chrome's hardware acceleration, graphics rendering, and background resource consumption before considering more drastic measures such as reinstalling macOS.

@samanth16: I had a similar sounding issue as soon as I moved to 27.2, as of the initial post upgrade reboot, and still an issue. But it only occurs when switching between different Chrome windows using Stage Manager. The tab it opens on will look ok, but any tab I then switch to (including switching back to the first one) will be blanked out and unresponsive (including won't reload). If I switch off Stage Manager and switch between Chrome windows in any other way, all is fine. Other web browsers behave just as they should - it is just Chrome which is affected. Toggling Stage Manager on and off consistently leads to this behaviour being 'broken' and 'fixed' respectively. There is nothing obviously different in to before showing up in Activity Monitor for Chrome. This is a 2020 Macbook Air, M1 Apple silicon.

I got this problem to resolve by disabling HW acceleration as you say, restarting chrome, then switched HW acceleration back on. Maybe Chrome's GPU cache got corrupted during the major update and this forced a rebuild? Not exactly 'diagnostic' but it's fixed.

Part 1 of 2

Open Activity Monitor (Finder > Applications > Utilities) and check the CPU and Memory tabs. Look for processes consuming unusually high resources, particularly Chrome Helper processes and background applications. Also check the Memory Pressure graph for yellow or red indicators and monitor swap memory usage. Runaway processes or memory leaks can contribute to system instability and application freezes. Apple's documentation explains how to monitor CPU activity, view memory usage, and identify running processes.

In this specific case look for Google, Google Chrome, Google Helper and Google Render

Part 2 of 2

Short and unpopular suggestion for some

 https://chromeisbad.com

May consider an alternative https://brave.com which is essentially Google Chrome without the Google baggage

Stop Chrome Browser From Downloading a Hidden 4GB AI File

Refer to the Posting by Respected Contributor @ John Galt 

Application memory error on my MacBook Pro - Apple Community

Refer to the Posting by Respected Contributor @ Kurt Lang

etrecheck... Mac running slow - Apple Community

1 - Google Chrome is overly aggressive in Resource and Memory usages.

2 - Google Chrome harvests all your personal data unbeknownst to you and sells your personal data,  which intern allows the Third Parties to Target you for their purposes 

Google Chrime. At least, that's what I'd call misappropriation of your data.

Chrome is a notorious resource hog on Macs. Installing it also installs multiple ‘helpers’ from Google that run in the background, and their purpose is not to help you but to help Google (keep in mind that Google’s primary source of revenue is using your data to drive targeted advertising). Even if you aren’t running the Chrome app, those system extensions are always running in the background. I’d recommend deleting Chrome and all related components.

https://chromeisbad.com

If you are looking for something other than Safari, consider Firefox or Helium (the latter is based on Chrome code but without the Google baggage). 

There is no solid evidence that macOS 27.2 is responsible for this issue.

Just because the problem started after an update does not mean the update caused it.

The issue occurs specifically in Chrome, and you have already disabled hardware acceleration without resolving it.

That makes it premature to blame macOS or assume an upcoming system update will fix it.

Have you tested Safari or another browser? Does the entire display go black, or is it only Chrome?

These are important distinctions before claiming this is a macOS graphics bug.

Unless the same issue can be reproduced outside Chrome or confirmed by Apple, blaming macOS 27.2 is speculation.

The problem needs to be isolated first.

Otherwise, this is simply an assumption based on timing, not evidence.

Thank you for the detailed troubleshooting suggestions.

I’ve checked the points you mentioned. I’m using a 15-inch MacBook Air with an M4 chip (2025). The issue occurs while using Chrome, where the screen suddenly turns completely black/stuck, although I can still switch between Chrome tabs.

I have already disabled Chrome’s hardware acceleration, but unfortunately, the issue still occurred afterward.

I haven’t yet checked Activity Monitor for CPU or memory usage, and I also haven’t tested the issue extensively with Safari or Safe Mode. I’ll try those steps and monitor whether the problem occurs again.

Since this started immediately after updating to macOS Golden Gate 27.2, I’m particularly concerned that it could be related to the macOS update or a compatibility/graphics issue.

I’d also like to know if other users with similar MacBook models have reported the same issue after this update, or if there is any known issue with macOS 27.2 itself that could be causing this behavior. If this is a software-related problem, is there any known fix or upcoming update addressing it?

I’ll update this thread with the results after trying the suggested steps. Thanks again for the help!

I haven't come across the same issue while using Safari so far. The problem appears to occur specifically in Chrome. I've also disabled hardware acceleration in Chrome, but that hasn't resolved it.

I agree that it's too early to attribute this to macOS 27.2. However, if the issue is isolated to Chrome, could you help me understand why this might be happening specifically in Chrome and what steps can be taken to identify and fix the underlying cause?

I'd appreciate a proper troubleshooting approach rather than assuming it's a macOS issue without evidence.