1404481 - Audios/Videos are crashing on FF ESR 52 on a Mac 10.13 device

Status: VERIFIED DUPLICATE of bug 1376163

(Core :: Audio/Video: Playback, defect)

Description

[Vijay]

Attachment: Screen Shot 2017-09-29 at 2.14.07 PM.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce:

 - Play any audio or videos, such as youtube


Actual results:

Browser just crashes


Expected results:

Audio or video should play without crashing the FF ESR 52 browser

Comment 1

[YF (Yang)]

https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[Vijay]

OS: Mac OSx 10.13
Browser: FF ESR 52

Comment 3

[Ryan VanderMeulen [:RyanVM]]

[Tracking Requested - why for this release]: Insta-crashes on Youtube

This has been reported to us by Apple too and I've gotten confirmation from others in #qa that can also reproduce. Trying to get ahold of a stack. jya mentioned that bug 1376163 might be related here, but the symptoms don't seem to fit.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Julien - possible issue for an ESR dot release. We should likely keep an eye on this.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

This is definitely related to sandboxing. I can easily reproduce this crash on a MBP w/ High Sierra and can confirm that changing the security.sandbox.content.level pref from 1 to 0 makes the crashes go away. Frustratingly, about:crashes isn't showing any reports when this hits, though, so I don't have any breakpad links to share :(

Comment 6

[Haik Aftandilian [:haik]]

I can reproduce the crash on an ESR 52 build. Before the crash I see the same audio sandbox violation as in bug 1376163 and the problem isn't reproducible with the fix for bug 1376163. Closing as a dupe of bug 1376163 which I'll post the ESR patch for shortly. And the crash is in mozilla::AudioStream::OpenCubeb().

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Confirmed that I no longer crash with CI builds containing the fix. Looks very promising that next week's ESR 52.4.1 release should fix this for affected users.