RESOLVED INVALID 219588
WebRTC using H.264 on M1 Macs with a built-in camera crashes
https://bugs.webkit.org/show_bug.cgi?id=219588
Summary WebRTC using H.264 on M1 Macs with a built-in camera crashes
Kevin Griffin
Reported 2020-12-06 20:52:23 PST
Created attachment 415536 [details] Safari WebRTC h.264 crash WebRTC in Safari and Safari Technology Preview on M1 MacBooks crashes when the codec used is H.264. Reproduction example: https://codepen.io/brainshave/pen/qBBWEpM This codepen allows you to select which codecs will be used to mirror you camera back you. On M1 Macs with a built-in camera, selecting H.264 and running the example will crash the page. You can uncheck "H.264" and run the example to see that VP8 and VP9 do not exhibit this behavior. This is 100% reproducable for me on a MacBook Air with an M1 chip. This happens in both Safari 14.0.1 (16610.2.11.51.8) and Release 116 (Safari 14.1, WebKit 16611.1.5.3) of Safari Technology Preview. This crash doesn't occur in Chrome's Apple silicon build, even with H.264 selected. A crash report from Safari is attached.
Attachments
Safari WebRTC h.264 crash (159.46 KB, text/plain)
2020-12-06 20:52 PST, Kevin Griffin
no flags
Radar WebKit Bug Importer
Comment 1 2020-12-07 02:57:05 PST
youenn fablet
Comment 2 2020-12-08 00:26:05 PST
Thanks for the report Kevin. Is the crash specific to the built-in camera? Can you try using the mock devices or USB cameras?
Szymon Witamborski
Comment 3 2020-12-09 00:19:57 PST
Hi Youenn, We did some extra testing and could confirm that it's *not* reproducible on: - M1 Air with mock devices - M1 Mini with external camera Hence our guess it might be related to the built-in camera in the M1 Air when encoding WebRTC streams with H264.
youenn fablet
Comment 4 2020-12-09 00:34:58 PST
Thanks Szymon, this is helpful
Kevin Griffin
Comment 5 2021-02-01 19:35:39 PST
I updated my M1 MacBook Air to macOS 11.2 today, and I no longer see Safari crashing with the codepen that Szymon provided.
Alexey Proskuryakov
Comment 6 2021-02-08 19:09:37 PST
Thank you for following up! Yes, this is fixed in macOS 11.2. I'm marking the bug as INVALID as it was a system issue below WebKit.
Note You need to log in before you can comment on or make changes to this bug.