1380070 - [10.13 Beta 3] With content sandbox disabled, Netflix fails on build 54/Release

Status: RESOLVED INVALID

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

Description

[Haik Aftandilian [:haik]]

With 10.13 High Sierra Beta 17A306f, with the content sandbox completely disabled (pref security.sandbox.content.level=0), Netflix fails to stream.

With the previous 10.13 Beta, Netflix streaming worked as long as the content sandbox was disabled. Bug 1376163 addresses the sandboxing issue, although only for Nightly and Beta. On Release/54, with the sandboxing fix, Firefox fails on Netflix. Root cause TBD.

Comment 1

[Chris Pearce [:cpearce (Not reading bugmail)]]

Does the CDM crash?

If the CDM doesn't crash, there's some other data that we can collect that may be useful; what does turning on MOZ_LOG=GMP:5,EME:5 tell us? If you press CTRL+ALT+SHIFT+L in the Netflix player their player log will display. Is there anything useful in there?

Comment 2

[Haik Aftandilian [:haik]]

(In reply to Chris Pearce (:cpearce) from comment #1)
> Does the CDM crash?

I don't see any indication of it crashing.

> If the CDM doesn't crash, there's some other data that we can collect that
> may be useful; what does turning on MOZ_LOG=GMP:5,EME:5 tell us?

Attached the log, but I don't think there's anything significant in it.

> If you
> press CTRL+ALT+SHIFT+L in the Netflix player their player log will display.
> Is there anything useful in there?

0.125|0|E|Storage| IndexedDB open error

Comment 3

[Haik Aftandilian [:haik]]

Attachment: 10.13 Beta 3, Firefox 54, Netflix failure, content sandbox turned off, MOZ_LOG=GMP:5,EME:5

Comment 4

[Chris Pearce [:cpearce (Not reading bugmail)]]

Ah! This failure happens when you run Netflix in the same profile in a newer then older versions of Firefox when the IndexedDB schema has changed between these version. So if you re-create a new profile, the new profile should work. You can also "forget about this site" for Netflix, and it should clear IndexedDB storage.

Netflix are planning on detecting this situation in their player and clearing the IndexedDB themselves when this happens, but they've got other higher priority things to deal with first...

Comment 5

[Haik Aftandilian [:haik]]

(In reply to Chris Pearce (:cpearce) from comment #4)
> Ah! This failure happens when you run Netflix in the same profile in a newer
> then older versions of Firefox when the IndexedDB schema has changed between
> these version. So if you re-create a new profile, the new profile should
> work. You can also "forget about this site" for Netflix, and it should clear
> IndexedDB storage.

Ah, thanks. Using a fresh profile worked for me. I don't normally use the same profile for different releases but I did when testing this on 10.13. Closing this bug.