Bug 232381 - iOS 15.1 WebContent crash if h264 video is negotiated
Summary: iOS 15.1 WebContent crash if h264 video is negotiated
Status: RESOLVED DUPLICATE of bug 231505
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Safari 15
Hardware: Unspecified Unspecified
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-27 08:33 PDT by Darius
Modified: 2021-10-27 22:06 PDT (History)
3 users (show)

See Also:

Attachments
Crash report (22.91 KB, text/plain)
2021-10-27 08:33 PDT, Darius 		no flags Details
Crash Report from iPad Air 4th Gen (37.00 KB, text/plain)
2021-10-27 13:37 PDT, Mitch Talmadge 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darius 2021-10-27 08:33:15 PDT 
Created attachment 442595 [details]
Crash report

The crash causes the page to refresh, and occurs just after ICE connection state becomes 'connected'.
It did not occur in iOS 15
Comment 1 Mitch Talmadge 2021-10-27 13:37:46 PDT 
Created attachment 442628 [details]
Crash Report from iPad Air 4th Gen

I am having the exact same problem, same segfault at the same location on an iPad Air 4th Gen in Safari or Chrome. 

My webapp was working on iOS 14.x but after upgrading to 15.1 it crashes some time during WebRTC negotiation. I have noticed this only happens when using the front camera; the back camera does not have this problem. 

I have found that turning off the experimental flag "WebRTC Platform Codecs in GPU Process" in the Safari settings makes the app work again.
Comment 2 Mitch Talmadge 2021-10-27 14:00:57 PDT 
I have created an example that causes this crash.

https://jsfiddle.net/o19c0wfe/4/
Comment 3 Mitch Talmadge 2021-10-27 15:42:24 PDT 
If I force VP8 to be used for WebRTC as in the example below, the crash no longer happens.

https://jsfiddle.net/MitchTalmadge/crpfvnab/21/
Comment 4 Sam Sneddon [:gsnedders] 2021-10-27 22:06:28 PDT 

*** This bug has been marked as a duplicate of bug 231505 ***