And the memory leak bug, it's getting quite annoying having to reboot after control center fills my RAM. - 14" MacBook Pro.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
M1 Pro and M1 Max MacBook Pro Owners Complain of Crashes Playing HDR YouTube Videos
- Thread starter MacRumors
- Start date
- Sort by reaction score
Am I interpreting this correctly? You say Apple needs to ask what the problem is, yet also state you won’t expend the time to explain (i.e., answer) if they would.
I don’t know of anyone that would disagree about the annoyance a DOA/faulty product can create. However, your sentiment defies reality. In other words, your expectation is based on the “perfect world” assumption. Most products are complex. Creating large-scale and mass producing products is especially difficult — which is nearly everything nowadays.
Here’s another way to think of it:
Steve Burke said:
With all of that said… In general, I think, Apple is now the same old corporation as the rest (e.g., Microsoft, Epic, EA). No core vision/passion, and every move is about $$$. Don’t be mistaken, business is always about profit. Although, a respectable/commendable business is one willing to make at least some sacrifices as well.
Last but not least. Just because people are loudly complaining about something on discussion/message boards/forums, the problem is not absolute widespread. If Apple completely ignores this problem and never fixes it, then you can be irate (I guess).
No. I am saying Apple is responsible for finding our why someone might be returning their stuff, but burden of reaching out nor the expectation of explaining shouldn't be placed on the customer.
I don't see how a functional working product is isolated to a perfect world. Either it works or it doesn't. There isn't a lot of gray there. The complexity of a product is more of a reason why it's not the customer's responsibility to identify the cause of a problem.
Of course, a company can (or should be able to) eventually figure out problems. However, the process (should) go quicker if the input and output surrounding the complaint is provided. Maybe try thinking of it this way… You go to the doctor and say, “It hurts!” They ask you for details such as: “What hurts?” “How long has it been hurting?” “How would you rate the severity?” You look at them angrily and say, “It’s your job to figure it out!” Again, yes, in general that’s true. However, the earlier questions help narrow it down. And instead of you providing information about how to narrow down the culprit, they say, “Okay. We’ll do [list off several dozen tests].” Many of those tests may be unreasonable to you, but to the person that lacks the details that’s how they’re going to determine them.
Not "a functional working product” rather every instance of every product. It’s just not possible. Evidently i.e., claimed) not every M1-based MBP/user of macOS Monterey is experiencing said problem. So, technically, Apple didn’t fail on the product design.
That's an analogy of tech support, not sales.
This mentality needs to stop. It's not ok to ship products that fail because software is hard.
For what it's worth, I have a gentle request. Can we cool it with the intellectual arguments and try to keep this thread focused on reports of the problem and possible solutions? I can share that I spoke with Apple today, that they are aware of this problem, and are trying to determine the cause.
It seems like it's a good idea to wait 6 months before trying the new versions of MacOS/iOS/iPad OS. Always seem to be buggy or missing all the advertised features.
Why do people think that posting ‘notes to Apple’ in other websites is a ‘productive thing to do’?!? Maybe go to Apple’s ACTUAL FEEDBACK PAGE and send them your feedback!! Otherwise you may as well tell your dog!
Also, I totally expect stuff like this will come up for a while as the new M1 MBP’s with OS Monterrey start to do more and more. It’s a brand new product, so you get to experience the bugs in real time. All this will probably be a non-issue in 6 months… if people actually reported these using official means, not Twitter rants.
Also, I totally expect stuff like this will come up for a while as the new M1 MBP’s with OS Monterrey start to do more and more. It’s a brand new product, so you get to experience the bugs in real time. All this will probably be a non-issue in 6 months… if people actually reported these using official means, not Twitter rants.
With that said… Relevant links:
I’m not sure which product the spotlighted problem would be most relevant to. It would depend if users have the same experience in Web browsers other than Safari — then go MBP feedback.
Product Feedback
We would love to hear your comments about any of our hardware and software products. Send us your thoughts.
www.apple.com
I’m not sure which product the spotlighted problem would be most relevant to. It would depend if users have the same experience in Web browsers other than Safari — then go MBP feedback.
Feedback - MacBook Pro
Apple wants to hear from you. Send us your comments and feedback about MacBook Pro.
www.apple.com
Thank you, I didn't go through all the posts due to this. Is it Safari that is the problem? Any browser? YouTube only? What about Apple TV HDR content?
After testing 10 machines (14 and 16 inch) only a single one did not crash.
The issue has nothing to do with scrolling the comments section. It happens under these circumstances:
This message has also been posted in the thread 14" MBP Kernel Crash
These machines reportedly crashed:
The issue has nothing to do with scrolling the comments section. It happens under these circumstances:
How to reproduce the CPU panic consistently within seconds
- In System Preferences > Displays the Refresh Rate must be set to "ProMotion" in order to reproduce the crash.
- In Safari* open any YouTube 8K HDR video.
- Select Settings/Quality/2160p60 HDR.
- Start playing the video. You may pause it.
- With the trackpad scroll down slowly. As soon as the video leaves Safari's blurry area behind the toolbar your MacBook Pro may crash. This is the critical part.
This message has also been posted in the thread 14" MBP Kernel Crash
These machines reportedly crashed:
- cababah
- GyroFX
- MK500, MBP 14", M1 Max, 32 core GPU, 32 GB RAM, 1 TB SSD
- davidako, macOS 12.0.1
- davidako, macOS 12.1 beta
- MBP14SAD, MBP 14inch, M1 MAX, 32GB, 1TB, MacOS 12.0.1
- tastylemon
- cuylerstuwe, macOS 12.0.1
- cuylerstuwe, macOS 12.1 beta
- UncleGuido, 16" M1 Max, 32GB, 1TB. Monterey 12.0.1
- walterpaisley, 14-inch M1 Pro (10/16, 16GB), macOS 12.1 developer seed
- kave, 16" 16GB RAM and 1TB
- TooManyNotes, 10-core 16" Max (32 GPU cores) with 32GB RAM, 1TB SSD
- playtech1, MBP 16
- imlfl
- Ancandis, 9x (MBP 14 base models (M1 Pro 8/10-core CPU), 16 base models (10-core CPU))
- Gorio, 14" 32GB 1Tb MBP
- pudcraft, Macbook Pro 16" M1 MAX 64GB
- JamieLannister, 1TB/16GB ram 10c/16c gpu MBP 16"
- rcoranje, MBP M1 pro 16 16 1TB
- dimplemonkey
- freyjaNeggy, MacBook Pro 16 m1 m1pro 16/32
- jgrove
- ams80, stuttering, base model 14"
- DMG35
- Ancandis, 16" M1 Pro 10-core cpu, 16 GB, 16 core GPU, 1 TB SSD
Last edited:
this froze my compact tabs default view too, interesting.
They still do:
Movie Trailers - Apple TV
Watch trailers for movies and TV shows on tv.apple.com. Browse trailers for upcoming TV series and films.
trailers.apple.com
Good job on reproducible steps. I can confirm this absolutely locked up my machine and then it rebooted. This is the first crash of any kind I have had on my 14" Max. It never happened to me before because I always went full screen when playing HDR content (and had played a lot of it). So it must have something to do with scrolling the content.
Thanks for confirming this.
For reference, this is a
MBP 14", M1 Max, 32 core GPU, 32 GB RAM
edit: w/ 1TB SSD
Last edited:
Those are my machine's specifications. With a 1TB SSD.
Poor little thing, it’s notch your fault. But the Safari 120hz/crashing issues aren’t notches on apples score card either!
My guess is that all these issues will be fixed asap, especially as it’s probably one of the first things many users would test out in store deciding wether or not to upgrade.
In my twisted mind, Intel paid Google a massive pile dollars from the marketing budget to cause this issue 
People think the internet, web browsers, and Linux are some neutral United Nations thing that’s a God given right.
They are not.
The internet and Linux requires selfless engineers to constantly improve and update the codebase for pennies on the dollar; possibly even working for free. If they don’t, the Linux OS and web render engines will fail to work with new hardware.
When was the last time you contributed code to Linux? When was the last time you added to Chromium?
3 of the top 4 internet browsers belong to major corporations: Google, Microsoft and Apple. They greatly compensate their engineers to keep things moving.
Skirting international laws to build a 100% private ecosystem on the world wide web is finally showing its true form.
Nothing works and no one will fix it.
So, now you have corporations lying on the package with claims of 4k resolution, and passing the blame to Microsoft, Apple, or Google. “It’s not our fault!”
To illustrate my point, building a web service on Mozilla is like building a sandwich empire on Boar’s Head and Wonder Bread.
At some point you have to cure your own meat and make your own bread.
If you disagree, explain how Mozilla should be funded for their free browser.
They are not.
The internet and Linux requires selfless engineers to constantly improve and update the codebase for pennies on the dollar; possibly even working for free. If they don’t, the Linux OS and web render engines will fail to work with new hardware.
When was the last time you contributed code to Linux? When was the last time you added to Chromium?
3 of the top 4 internet browsers belong to major corporations: Google, Microsoft and Apple. They greatly compensate their engineers to keep things moving.
Skirting international laws to build a 100% private ecosystem on the world wide web is finally showing its true form.
Nothing works and no one will fix it.
So, now you have corporations lying on the package with claims of 4k resolution, and passing the blame to Microsoft, Apple, or Google. “It’s not our fault!”
To illustrate my point, building a web service on Mozilla is like building a sandwich empire on Boar’s Head and Wonder Bread.
At some point you have to cure your own meat and make your own bread.
If you disagree, explain how Mozilla should be funded for their free browser.
This is why:
Microsoft collects 30% on Xbox
Nintendo collects 30% on Switch
Apple collects 30% on iOS
Google collects 30% on Android
Sony collects 30% on Playstation
Samsung collects 30% on Galaxy
etc.
Microsoft collects 30% on Xbox
Nintendo collects 30% on Switch
Apple collects 30% on iOS
Google collects 30% on Android
Sony collects 30% on Playstation
Samsung collects 30% on Galaxy
etc.
Maybe Apple waives the 30% fee for Safari users on MacRumors, since it contributes directly to their ecosystem.
At the same time, Microsoft engineers visiting MacRumors on Edge are not actually helping Apple.
It could literally be handled in the ad exchanged on browser type.
At the same time, Microsoft engineers visiting MacRumors on Edge are not actually helping Apple.
It could literally be handled in the ad exchanged on browser type.
An recent MKBHD video crashed my safari a couple times. M1 MacBook Air.