Closed
Bug 1452828
Opened 8 years ago
Closed 8 years ago
Many Videos on Facebook fail with NS_ERROR_DOM_MEDIA_FATAL_ERR
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mozilla.bugzilla, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180323154952
Steps to reproduce:
On MacOs 10.13.4, Firefox 59.0.2, with new, default profile:
Log in to Facebook.
Go to https://www.facebook.com/JungleVT/videos/2572410969567396/
Enable DRM when requested to do so (right-edge button in yellow alert-bar)
Attempt to play video by clicking on play button.
Notice that gmp-widevinecdm/1.4.8.1008 and gmp-gmpopenh264/1.7.1 are installed.
Actual results:
Video "loading" spinner spins, then stops and disappears.
Video does not play.
Play button appears. (If pressed, same thing happens.)
In console, error message appears:
[Child 11540, MediaPlayback #2] WARNING: Decoder=127bd2c40 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - void mozilla::EMEDecryptor::AttemptDecode(mozilla::MediaRawData *): Failed to convert encrypted AAC sample to ADTS: file /builds/worker/workspace/build/src/dom/media/MediaDecoderStateMachine.cpp, line 3453
[Child 11540, MediaPlayback #3] WARNING: Decoder=15c02a7a0 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - void mozilla::EMEDecryptor::AttemptDecode(mozilla::MediaRawData *): Failed to convert encrypted AAC sample to ADTS: file /builds/worker/workspace/build/src/dom/media/MediaDecoderStateMachine.cpp, line 3453
Expected results:
Video should have played. (In Chrome 65.0.3325.181, it autoplays on page load).
Comment 1•8 years ago
|
||
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180412232808
Hello Brad,
I have tested this issue on latest Firefox release 59.0.2, latest Nightly build 61.0a1 and could not reproduce it. I have logged into my Facebook account, navigated to the provided link and everything worked as expected: the loading spinner appeared and afterwards the video started to play. However, I had no notification regarding enabling DRM and maybe this is the reason why I didn't manage to reproduce this issue.
I've tested this with Widevine Content Decryption Module provided by Google Inc. 1.4.8.1008 and OpenH264 Video Codec provided by Cisco Systems, Inc. 1.7.1 from the "about:addons" page -> Plugins tab, both with "Always Activate" and "Never Activate" options.
Just to be sure, on the new default profile, did you have some add-ons installed? Also, did you change some settings in your browser in order to get the DRM notification?
If you don't mind can you please retest this and while doing it use safe mode (https://goo.gl/AR5o9d), to eliminate custom settings as a possible cause and report back the results?
Thanks.
Flags: needinfo?(brad)
Hmm. Now, the Facebook video mentioned in the "Steps to reproduce" doesn't use DRM at all (it plays with DRM disabled, and the libwidevinecdm.dylib is not loaded). That makes me think Facebook had a transient video production error, which perhaps applied broken DRM.
That said, while they were applying DRM, I'm guessing I was seeing the problem in Bug 1447821, which i am still able to reproduce (with the same error message as this bug, FF 59.0.2) on my clean profile.
So I assume this bug is a duplicate of 1447821.
Flags: needinfo?(brad)
Comment 3•8 years ago
|
||
Hello Brad,
Thanks for answering. It seems that the mentioned bug is fixed in Firefox 60 and 61. Could you please confirm if you're still encountering this issue on latest Firefox Beta 60.0b12 (https://www.mozilla.org/en-US/firefox/channel/desktop/#beta) or latest Nightly build 61.0a1 (https://nightly.mozilla.org/)?
Thanks.
Flags: needinfo?(brad)
I have tested against FF 60.0b12, and this appears to be resolved. Thanks!
Flags: needinfo?(brad)
Comment 5•8 years ago
|
||
Thanks Brad for the confirmation. Based on comment 4, I'm changing the status to RESOLVED WORKS FOR ME.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•