After upgrading to 26.1 accessing the Web-UI using Chrome on MacOS (Sequoia 15.7.4) is no longer possible.
However, Chrome on Linux (Fedora flavor) works just fine.
The Web-UI manages something I have not seen any browser UI do before. It not only kills the tab but it effectively kills the entire browser process. It first causes the UI lements of the browser to start flickering and soon the entire browser becomes grey. Most likely it is able to trigger some existing low level graphic layer bug in MacOS.
I have tried re-starting the browser both removing all add-ons as well as running in Incognito mode with the same result.
Using Firefox on MacOS (or Chrome on Linux) works just fine.
Is this only a "me" problem or are others affected as well?
Quote from: jj162 on March 01, 2026, 03:30:43 PMI have tried re-starting the browser both removing all add-ons as well as running in Incognito mode with the same result.
Does Google Chrome have any of the following :
- Safe Mode ?
- The option to create a new fresh clean Profile ?
Or maybe try with Chromium instead of Google Chrome ?
Microsoft Edge also uses the same engine so you could try that too!
Im using Chrome on a latest version Macbook daily since I develop for OPNsense on it. If things would break I'd notice immediately.
For reference Im using:
Chrome 145.0.7632.117 arm64
MacOS 15.7.4 on an M2 Max
I did clean the cache & cookies, used an incognito tab (which uses (an almost) clean environment, afaik there is no other way to get it even more clean), disabled the few plugins I use (adblock & dark theme) but still the same result. Since it works on Linux (all browsers) and on FireFox on MacOS it seems to only affect Chrome on (old) Intel MacBook Pro with MacOS 15.7.4 (The old 25.7 OpnSense works fine)
For anyone interested you can see a short screen recording of how the browser is killed here: https://drive.google.com/file/d/1O06O69hZzvEV5cdpssSjTAT3h0wwd1nF/view?usp=sharing
I'm running on an Intel MacBook Pro, MacOS 15.7.4 (24G517), Chrome Version 145.0.7632.117 (Official Build) (x86_64).
But, since there are workarounds and it seems to only affect the dwindling Intel MacBook Pro population (It works on an Intel Mac Pro with Chrome) I don't feel this is a high priority, so, lets just call it a feature!
Did you try disabling "Use graphics acceleration when available."?