Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yesterday I received a 14” M1 Max and it crashes every single time I play 2160p60 HDR content on YouTube and use Multi-Touch to “show desktop” but only if the safari window where YouTube is running hides in a upwards motion (towards the menu bar)

It didn’t crash while scrolling.
It didn’t crash when entering or exiting full screen.
It didn’t crash when I used Multi-Touch to show the desktop if the safari window hides to left or right side of the screen or in a downwards motion.

It does however crash every single time the safari window is sent in an upwards motion towards the menu bar by the “show desktop” Multi-Touch gesture.
It happened with both MacOS 12.0 and 12.0.1.

Did anyone else experienced this behaviour and can someone who claimed that their laptop didn’t crash test the scenario I’ve described to see if it still doesn’t crash?
Thanks
 
  • Like
Reactions: TooManyNotes
How about YouTube dark mode?

I just tried several 4K HDR videos in YouTube dark mode, macOS in light mode. No panics. The same videos caused panics on my 16" Macbook Pro M1 Max with the recipe posted by Ancandis, when YT was in light mode.
 
  • Like
Reactions: lowimpact
I just tried several 4K HDR videos in YouTube dark mode, macOS in light mode. No panics. The same videos caused panics on my 16" Macbook Pro M1 Max with the recipe posted by Ancandis, when YT was in light mode.

For me; either YouTube in dark mode or MacOS in dark mode stops Safari from crashing, but not Chrome
 
  • Like
Reactions: lowimpact
I remember a time when more people (like those above) tried to isolate/solve problems rather than post inane comments. That IS cool.

Hat tip to JamieLannister, Ancandis, and others for putting in the work!
So why did you post an "inane comment"?
 
Does this mean we can finally jailbreak M1 Pro/Max into "sideloading" IPA files? It's laughable that Apple puts an artificial restriction on what you can do with your $3500 computers.
Because if you don't people like my mom will "sideload" something on the internet and have all her life savings stolen from her. It literally happened to her. The only reason why she didn't get all the money stolen was because Apple wouldn't let her install the malware.

My mom called me to ask my she couldn't install the software, and then I realized that someone was trying to get her to install the malware to withdraw money from her bank account.

Is that a good enough reason or are you gonna use the "buyer beware" argument?

Not all computers users a tech literate. People make mistakes.
 
I appreciate the effort, but you were using the Compact tab layout setting, which several people have already identified as being a workaround.
Everything works perfectly fine here. Offline I also disabled all extension after this recording. No crashes - good luck, I have done all the test here. Works fine for me.



Either the person laptop hardwares are defect on the GPU cores bad binned - faulty die or bad memory.
 
  • Like
Reactions: IG88
Everything works perfectly fine here. Offline I also disabled all extension after this recording. No crashes - good luck, I have done all the test here. Works fine for me.
Either the person laptop hardwares are defect on the GPU cores bad binned - faulty die or bad memory.

I see you're in Canada. Gonna need you to move to the US and try it. Lol, j/k. I agree that yours isn't having the issue. But I don't agree that it has to be hardware.

I was having kernel panics on my 2018 15" MBP and Apple eventually addressed it with an update. The "BridgeOS" debacle.
 
Last edited:
just ran this on my base M1 Pro 16 (only upgrade is 1TB SSD) - works fine. In fact I was playing this 8K HDR in two places and the machine suffered no slow downs other than loading comments.
 
M1 Pro 16GB/1TB 10c/16c 16" model with promotion on, HDR 1600 profile set, on power, on battery tested. NO ISSUES AT ALL PERIOD. I believe this may be a real hardware issue with some models sold. I have not had one single restart/crash while watching full HDR content at max including VLC using yt-dlp downloaded webm/mp4 8K footages off YouTube. AV01 format won't play in QuickTime however. VLC will allow VP9.2 playing with HDR.

Another new 8K video I tried that has zero issues full screened, theatre mode, default view mode, all while scrolling slowly and/or quickly in comments section - nothing restarts or crashes on my MBP 16.

I'm trying all these as well and no crash - I get slight scroll stutter when slowly panning back up from the comments to the video - when it first appears out of the tab/address bar area it lacks some smoothness (when scrolling slowly).

I have same model as you. No issues in any video I've tried and I'm on 12.0.1
 
At this point, it seems fair to say the issue does not affect all machines. If it did, I think there would be more widespread complaints. I would also expect comments from the more prominent YouTube reviewers who presumably would be testing a lot of HDR content on the platform through which they make a living.
 
Want to jump into a new MBP, but after dealing with a few Apple service programs over the years this browser crashing issue is more than a little concerning.

Since there isn't any vlogger / influencer chatter about this is the assumption that only a minority of hardware is affected and that apple will replace affected units and/or release software updates addressing the issue promptly?
 
Want to jump into a new MBP, but after dealing with a few Apple service programs over the years this browser crashing issue is more than a little concerning.

Since there isn't any vlogger / influencer chatter about this is the assumption that only a minority of hardware is affected and that apple will replace affected units and/or release software updates addressing the issue promptly?
The Apple rep I spoke to said they were aware of the issue and investigating, and that hopefully it's something that can resolved with an update. If it ends up being hardware, he said the 1-year warranty would cover me. It still left me a little nervous; what if they later refuse to recognize the issue? I am thinking of returning mine and waiting a month for a replacement. Will be painful because I love this machine.
 
  • Like
Reactions: Gorio
I'm just going to watch the HDR videos without scrolling for now, until an update fixes these issues. Don't need to see what others have to say anyways lol
If only it were about ignoring comments. It also prevents one from reading additional information posted by the author (ie. product links, video links). Also prevents one from scrolling down to see additional video recommendations.
 
If only it were about ignoring comments. It also prevents one from reading additional information posted by the author (ie. product links, video links). Also prevents one from scrolling down to see additional video recommendations.
I'm not ignoring the issue, just in the mean time since nothing else is causing any issues... yet. I still have my case number opened with Apple and a rep that's assigned to me with any updates regarding this issue. I've spent a few hours last weekend going through my freezing with the rep and sending in diagnostic info to Apple. Rep said the engineers are still investigating this since it's been reported to them. I guess I'm just going to wait around for the official 12.1 update before going further with this.
 
Make sure to set your display to ProMotion (120 Hz), open an 8K HDR video in YouTube and set the video resolution to 2160p60 HDR while in the browser window and scroll _slowly_ upwards so the video will disappear under Safari's menu bar and then some more.

Any 8K HDR video will do. I have used the one that always pops up first for me (Peru).

edit: this video
Yes - this is an issue.
 
I'm not ignoring the issue, just in the mean time since nothing else is causing any issues... yet. I still have my case number opened with Apple and a rep that's assigned to me with any updates regarding this issue. I've spent a few hours last weekend going through my freezing with the rep and sending in diagnostic info to Apple. Rep said the engineers are still investigating this since it's been reported to them. I guess I'm just going to wait around for the official 12.1 update before going further with this.
My apologies if my comment came across that way, I truly wasn't trying to suggest you were ignoring the issue. I meant to express it matter-of-factly, but there was probably some emotional irritation that snuck in there... not with you, just the situation :)
 
16 inch base M1 Pro crashing as well. Switched to compact tabs - so far no issues. Doubt this will warrant a return from me. I already returned twice due to scratches. Plus there aren't any near me within 50 miles.
 
Last edited:
Well I guess anyone who bought their MacBook Pro on launch day is out of the return window. Hope there’s a software fix
 
Well I guess anyone who bought their MacBook Pro on launch day is out of the return window. Hope there’s a software fix
Bought mine on 2nd day, no issues so far.

I recommend people reset and refresh the MacOS and try again.
 
There's so many posts in this thread attempting to explain this issue with nothing more than supposition and guesswork behind it, yet there are ways to determine why this is happening.

I don't know if these crashes are all occurring for the same reason, but let's assume they are. We can take a look at the crash report:

Code:
panic(cpu 0 caller 0xfffffe002f2d7d68): DCP PANIC - IOMFB int_handler_gated: failure: axi_rd_err [0x40000634]
 - iomfb_driver(8)
IOMFB int_handler_gated: failure: axi_rd_err [0x40000634]

RTKit: RTKit-1826.40.9.debug - Client: local-t600xdcp.release
!UUID: 63c86ca9-4c8f-33e2-9b03-9b1e9da40cfa
Time: 0x00000000764d6c69

I am not a developer, but I have worked in computer science for more than 20 years so hopefully I can work through this somewhat.

We can see from the crash report that the failure is in RTKit, which is kind of like a miniature operating system where various co-processors run. These co-processors are part of the M1 SoC and include things like the video encoders and decoders, the power-management processor, and the secure enclave.

Within one of these RTKit instances will be the subsystem responsible for on-screen graphics, which will obviously communicate directly with the physical GPU. Part of that subsystem is the IOMFD (IOMobileFrameBuffer.) Based on the name alone, I'm guessing this is where the image to be displayed on the screen is stored.

Finally, we can see that the the IOMFB driver has an error: axi_rd_err. AXI is the Advanced eXtensible Interface, which is a low-level communications interface specifically for ARM chips. rd_error indicates a read error.

So putting this all together, my estimation is that the there is essentially a problem with the display driver. It seems to be attempting to read something from the framebuffer which isn't there.

The problem in trying to understand this further is that a lot of this stuff is undocumented outside of Apple and, frankly, I'm also at the limit of my ability to troubleshoot. But nonetheless, I'm quite sure that once Apple gets hold of these crash reports, a simple driver update will sort this out. Even if the highly unlikely event that this was a hardware issue, a driver update would allow the operating system to simply anticipate and work around the problem.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.