Closed Bug 1671230 Opened 4 years ago Closed 4 years ago

Playback failing on Firefox browser v.81 - "ns_error_failure"

Categories

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

Firefox 81
defect

Tracking

()

RESOLVED DUPLICATE of bug 1714125

People

(Reporter: spoc_rte, Unassigned)

References

()

Details

(Keywords: parity-chrome)

Attachments

(7 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

Open Firefox v.81
try to play this VOD
https://www.rte.ie/player/series/nationwide/SI0000001172?epguid=IH000382899

Actual results:

Several Video-On-Demand assets are totally failing and we get the following error message once selected : "ns_error_failure (0x80004005).
This not happen with other MPEG-DASH Streams (Chrome for example)

Expected results:

The playout should be clean and without error as happen on other browsers (Chrome)
Note that this happen also wiht other version of Firefox (v80, v79).

Attached file HAR session

IF you need further info concerning streaming, please refer to unified support person, as per email provided.

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
20201014095212

It plays in Vivaldi 3.3. In a brand new profile in the latest Nightly, clicking the Play button results in "Something went wrong during native playback." being displayed instead of the video. Accoding to the Browser Console errors, you're sending the wrong Content-Type.

HTTP “Content-Type” of “application/dash+xml” is not supported. Load of media resource https://vod.rte.ie/…&hls_fmp4=true failed. SI0000001172

VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) Something went wrong during native playback. 
Object { code: 4, message: "Something went wrong during native playback." }
main-es2015.0760069d7896d019da68.js:1:1506759

Cannot play media. No decoders for requested formats: application/dash+xml, application/dash+xml SI0000001172
Has STR: --- → yes
Component: Untriaged → Audio/Video: Playback
Keywords: parity-chrome
Product: Firefox → Core

I'm not able to reproduce this, but based on the attachment and Gingerbread Man's comment, it appears to be an error on the part of the site trying to provide the wrong type of data to a media element.

Additionally, it appears that page uses DRM, so I wonder if that could be part of the problem. Can you share the output from about:support in your browser where you're having the problem?

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
20201017213521

(In reply to Jon Bauman [:jbauman:] from comment #3)

Additionally, it appears that page uses DRM, so I wonder if that could be part of the problem.

I can play the video now. Previously, Widevine had failed to install at comment 2.

Attached file my:about_support
Dear support, please let me provide another case. This is another video that is failing on firefox 81 and not on chrome The video is DRM'd.: https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027 I've also get firefox debug log for that. Please get from this url while the playout https://rte-ngrp-fincons-usp-share.s3-eu-west-1.amazonaws.com/unified/31412/l2v_IH000383027_notworking/IH000383027_firefox.log_ Furthermore as you requested, please find the about:support output
Attached file firefox_debug.log
Dear support, please let me provide another case. This is another video that is failing on firefox 81 and not on chrome The video is DRM'd.: https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027 I've also get firefox debug log for that. that can help you on analysis on what's going on https://rte-ngrp-fincons-usp-share.s3-eu-west-1.amazonaws.com/unified/31412/l2v_IH000383027_notworking/IH000383027_firefox.log_ Furthermore as you requested, please find the about:support output from attachment.

Dear support,
please let me provide another case.
This is another video that is failing on firefox 81 and not on chrome
The video is DRM'd.:
https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027

I've also get firefox debug log for that. that can help you on analysis on what's going on.
Furthermore as you requested, please find the about:support output from attachment.

On log the error is something related to video codec:

[Child 8383: Main Thread]: D/MediaSource dom::SourceBuffer[0x148cf7100] (video/mp4; codecs="avc1.64000D")::QueueAsyncSimpleEvent: Queuing event 'error'
[Child 8383: Main Thread]: D/MediaSource dom::SourceBuffer[0x148cf7100] (video/mp4; codecs="avc1.64000D")::QueueAsyncSimpleEvent: Queuing event 'updateend'
[Child 8383: Main Thread]: D/MediaSource dom::MediaSource[0x1546a3890] ::EndOfStream: EndOfStream(aError=NS_ERROR_FAILURE)

Hi Support,
did you have any update on that?

I still can't reproduce the error on the original link (https://www.rte.ie/player/series/nationwide/SI0000001172?epguid=IH000382899), and I'm getting invalid certificate errors which are preventing me from accessing the test cases on test.rte.ie.

Severity: -- → S2
Priority: -- → P3

Hi Jon,
Issues on test environment has been fixed. Now you can test yourself this asset:
https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027

On Test we have a basic authentication. This is the user: firefox
How can i share password information? Can i use email or another system?

Thanks,
,s

Hi Jon,
i just get from your account email. I've sent to you password for environment.
Please let me know for any issue.
.s

Attached image Safari-14.0.png

https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027 doesn't successfully play in Firefox (83.0a1), Chrome (86.0.4240.75) or Safari (14.0) (all on macOS). Though the failures aren't 100% consistent (see attached screenshots), I'm fairly confident in saying the issue isn't the browser.

Dear Jon.
I'm sorry for this inconvenient. This was caused for an issue on overall the test environment that now has been solved.
All the asset backs to work as expected again, including the example i gave you last days:
https://test.rte.ie/player/series/prime-time/SI0000000825?epguid=IH000383027

I can confirm that this assett doesn't work on any firefox version, but work perfectly on chrome.
The assett is DRM protected, as i told you before.

Please, try to test it again and apologize us again for inconvenient.
Regards,
.s

Dear Support any updates?
thanks.
.s

No updates at this time. Rest assured that they'll be posted here when there is additional information to share.

Hi Jon,
Did had time to look at that? Did you find any evidence.

Thanks,
S.

Hi Support,
any update on this? We are not receiving update since long time.
Thanks.

Dear Support,
we didn't receive any feedback yet. Can you confirm that you are looking at the case?
I need to report the status .

thanks,
.s

Hi spocrte,

Yes, this is being looked at, but I can't give you any sort of a timetable for when to expect a resolution. I see you're new to bugzilla, so let me offer some context that may help make the situation more understandable. As much as we wish we could, we don't have the resources to fix every bug immediately, which is part of why our Bugzilla Etiquette page mentions our "no obligation" principle:

"Open Source" is not the same as "the developers must do my bidding." Everyone here wants to help, but no one else has any obligation to fix the bugs you want fixed. Therefore, you should not act as if you expect someone to fix a bug by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact of and interest in your suggestions.

I know you're eager to have this resolved or at least to have a better idea of when you'll know more. If the issues is with Firefox, the best way to help would be to provide as specific information possible about the browser behavior mandated by the relevant web standards and how Firefox is out of compliance. Or, to create the simplest possible use case that reproduces the issue. I realize both of those may be difficult tasks, and we'll still do our best to fix it on our own, but the best way to get this issue resolved as soon as possible is to provide any information you can to help clarify what exactly is causing the problem and refrain from comments that don't contribute to that shared goal.

Thanks for your understanding, and thanks for working to make the rte.ie experience for Fixefox users great.

Currently the test site is failing on Firefox, Safari and Chrome. It looks like it's getting 503s on the requests like this one. I'm pretty sure that's unrelated to the original error, but since I can't reproduce the issue on the production site, my investigation of this is stalled until the test site is working again.

Flags: needinfo?(spoc_rte)

Dear Support,
we had a infrastructural problem on latter days. Now the asset is streamable again. We just tried again on firefox and issue is shown as usual.
Would you please try again?
Thanks.
.s

Flags: needinfo?(spoc_rte)

Dear Support, did you have tried to stream again? Where you able to reproduce the problem?
Thanks,
.s

Is this still an issue?

Flags: needinfo?(spoc_rte)

Hi Bryce, I confirm we still have the same issue. You can test it using our test environment:

https://test.rte.ie/player/

The player is behind basic authentication, you can use the same credentials shared a few months back (user: firefox , password: sent to your account email a few minutes ago).

You can replicate the issue using this asset: https://test.rte.ie/player/series/dr-phil-%28bornvod-slate%29/qwafghj?epguid=AQ000270299

It plays correctly on Chrome, Safari and other browsers. We tried different players too, everything is fine. On Firefox it breaks right away with error:
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) NS_ERROR_FAILURE (0x80004005)

I tried with the current developer version and the stable one, both on Linux and Windows. Same error on all platforms.

It looks like something related to the DRM/widevine component, the same asset without DRM plays correctly.

Let me know if you need anything else.

Thank you for your help!
Fabio

Flags: needinfo?(spoc_rte)

Thanks. I'm looking at another issue that may be related. I will update this bug if I find there is a connection.

I believe this is the same issue as bug 1714125. Since I've got a patch against that bug, I'm going to dupe this and track further work in bug 1714125.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: