Just had this happen first time ever. Menu bar went straight pink. WTH? Rebooted and it's gone. M3 MBA Sequoia 15.3.1
Same here; menu bar 'came back' after switching application. Ever since 15.3.1Just had this happen first time ever. Menu bar went straight pink. WTH? Rebooted and it's gone. M3 MBA Sequoia 15.3.1
I now wonder if this an application specific bug.Same here; menu bar 'came back' after switching application. Ever since 15.3.1
;JOOP!
Indeed, I have to record when exactly it happens.I now wonder if this an application specific bug.
I found that it happens when FireFox is active; the effect stops (bar visible again) when you blindly click on the app'sI now wonder if this an application specific bug.
I bet that has something to do with Firefox's ability to switch between modern titlebar and classic titlebar.I found that it happens when FireFox is active; the effect stops (bar visible again) when you blindly click on the app's
name 16 mm right from the left upper screen corner.
Any more? Anyone else?
;JOOP!
I wonder ... I never switched anything in Ff's themes for 14 years.I bet that has something to do with Firefox's ability to switch between modern titlebar and classic titlebar.
Funny: I fail to reproduce the problem at will.I bet that has something to do with Firefox's ability to switch between modern titlebar and classic titlebar.
Well, Murphy's Law hates both of us.. and I thought it was only me, lol.Funny: I fail to reproduce the problem at will.
;JOOP!
Well, if you think about it, where is the Firefox menu bar? It's right smack in the middle of the area that Firefox can allow you to hide when choosing the modern title bar.. the very thing that is turning pink on your system. This bug is Mozilla's fault.. and their childish tinkering "to make things better". Really, a pink menu bar is "better"?I wonder ... I never switched anything in Ff's themes for 14 years.
;JOOP!
I did not see it (yet) since Firefox 135.0.1 (today's update).This bug has been present since Sonoma. It's interesting that it happens on M series Macs too, I thought it was only on Intel... Sometimes the menubar turns red, sometimes part of it turn purple, clicking anywhere makes it go away, and it reappears after a while, but I suspect it's a GPU memory thing, I don't know how or why though. I'm surprised it hasn't been fixed, since there's no way Apple is not aware of it. It's not related to Firefox or any kind of specific app.
Oddly enough, I found that the ONLY workaround (for me at least) that works is to use a desktop picture forcing the menubar to appear white-ish, or "light" to use the terminology of light/dark appearance (for instance I use a desktop picture with a 25px light stripe at the top, which automatically turns the menubar white, regardless of the appearance I choose in system settings). I have absolutely no idea what causes this bug but if you have an "always on" white menubar, this bug goes away. It's too bad because I like the default transparent one, but I don't like that kind of cosmetic glitches either...
So it must be the application(s); I filed a bug report to Mozilla, referring to this thread.On my 2019 Intel MBP with Vega 20 GPU, I’ve noticed my menu bar will temporarily turn red after starting up or exiting Mozilla VPN. I think it’s also happened when exiting Affinity Photos app. I’ll pay attention to when it happens and what apps cause it. Started doing this with Sonoma if I recall. I also notice that occasionally when I exit a program the left side of my menu bar looks pixelated and low resolution, and returns to normal after I launch a new application. I thought maybe it was related to AMD drivers or something with Intel MBPs. Doesn’t exhibit this behavior in Mojave through Monterey (I skipped Ventura).
It happens with so many apps (Adobe, Safari, Cubase, Pro Tools, Apple's Photos, Mail, Logic, the list goes on...) and more and less randomly. I can't believe Apple hasn't addressed this. I guess it's something with the windowserver, or vram, or I don't know what else. Since Apple is silent maybe some 3rd party developers can shed some light on this issue, so fingers crossed with your bug report...So it must be the application(s); I filed a bug report to Mozilla, referring to this thread.
See what happens next.
;JOOP!