Closed Bug 1732492 Opened 4 years ago Closed 3 years ago

Firefox throws the "NS_ERROR_OUT_OF_MEMORY" error when playing Video content

Categories

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

Product:
Core
Component:
Audio/Video: Playback
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1697476

People

(Reporter: dv-web-players+mozilla, Assigned: bryce)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36

Steps to reproduce:

I haven't been able to reproduce this on my machine since I don't know what causes it but we have seen this occur most commonly when people try to play a live content on Prime Video. However, it isn't exclusively happening on Live content. We've seen it on Mac and Windows OS and various Firefox versions (most commonly 92).

Possible steps to reproduce:

Use Firefox on Windows or Mac machine.
Sign in into Amazon.com/video with any amazon prime account.
Play a free live title included with Prime Subscription. Eg: Any live game event such as NFL.
Monitor the console log and look for "NS_ERROR_OUT_OF_MEMORY (0x8007000e)".

Actual results:

The NS_ERROR_OUT_OF_MEMORY (0x8007000e) error causes the player to quit unexpectedly.

Expected results:

Player should continue playing the content with no interruptions.

Hi dv-web-players-mozilla,
I tried to reproduce on Windows 10, using Nightly 94.0a1 (2021-09-27) (64-bit) and Release 92.0.1 (64-bit) versions, and I was unable to reproduce it. I could login and attend to some shows, but mentioned error from your actual results is not occuring. I was unable to stream a live game event due to region problems.
Could you answer the following questions in order to further investigate this issue?

  1. Does this issue happen with a new profile? Here is a link on how to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

Can you test the issue while in Safe Mode (Safe Mode disables add-ons, extensions and themes, hardware acceleration and some JavaScript stuff in order to exclude some possible reasons for problems). You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode.

  1. Does this issue occur in the latest nightly version of firefox? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/

  2. Are you using any addons? If so, please list them. Please, can you go to Help -> More Troubleshooting Information and copy at least the "Add-ons" information into an attachment here?

  3. If you are still able to reproduce it, please, share an specific link to video, maybe another one different than Amazon site, in order to get the error in console.

I've assigned a component in order to get the dev team involved.
'Core-Dom:Streams' team: if the component is not relevant please change it to a more appropriate one.

Regards.

Component: Untriaged → DOM: Streams
Flags: needinfo?(dv-web-players+mozilla)
Product: Firefox → Core
Version: other → unspecified

Hi, If you follow this link and subscribe to one of the live sports channel, you can see available live sports in US: https://www.amazon.com/gp/video/storefront/ref=atv_hm_hom_c_tas3lp_8_smr?contentType=merch&contentId=pvsports&merchId=pvsports. We have seen this issue happen more frequently on live content so it might be helpful to try to repro using live link.

Answer to your questions:

  1. I'm not sure. We haven't reproduced this issue locally and we would need to reach out to Amazon users to know if this issue happened with a new profile. I can try to find this out.
  2. This issue wasn't specific to any Firefox version. We saw it happen most commonly on Firefox 92.
  3. Again, we haven't reproduced this so not sure. I can try to find this as well.
  4. This would be difficult since the live event is over. If I'm able to get one for another live event or any other content, I will share it here.

Thanks!

Flags: needinfo?(dv-web-players+mozilla)

Hi,
currently I'm unable to subscribe to one of the of the live sports channel, thanks for the link anyway.
Could you confirm or check any of the questions from comment #1?
Please, any additional information, let us know.
Regards,
Jerónimo.

Flags: needinfo?(dv-web-players+mozilla)

Hi,

We were able to reproduce this issue internally. For your questions from comment #1:

  1. No, the issue isn't related to a new profile. Yes, it happened when using the browser in safe mode as well.
  2. No, the issue occurs in Firefox version 91.0 so it's not the nightly version.
  3. The addons that were being used are:
Name 	Type 	Version 	Enabled 	ID
Amazon.co.uk	extension	1.9	true	amazon@search.mozilla.org
Amazon.com	extension	1.3	true	amazondotcom@search.mozilla.org
Bing	extension	1.3	true	bing@search.mozilla.org
DuckDuckGo	extension	1.1	true	ddg@search.mozilla.org
eBay	extension	1.3	true	ebay@search.mozilla.org
Google	extension	1.1	true	google@search.mozilla.org
Wikipedia (en)	extension	1.1	true	wikipedia@search.mozilla.org
Greasemonkey	extension	4.11	false	{e4a8a97b-f2ed-450b-b12d-ee082ba24781}
U2F Support Add-on	extension	1.0.1	false	u2f4moz@prefiks.org
  1. We saw this reproduce in last week's Thursday Night Football live game. This is the link for the event this week if you want to attempt to reproduce it: https://www.amazon.com/gp/video/detail/B09B2ZV2HL/ref=atv_hm_hom_1_c_ZWyNDQ_fMonMk_1_1. Again, any live event can be used to try to reproduce this.

We don't see any Mozilla logs and our internal logs don't point to any issue happening in the player. The only code we see is errorCode: 3. NS_ERROR_OUT_OF_MEMORY (0x8007000e). Please let me know if there is any way we can help in getting logs or root causing the problem.

Flags: needinfo?(dv-web-players+mozilla)

(Changing this component, as DOM Streams currently has no live code in Firefox as shipped)

Component: DOM: Streams → Audio/Video: Playback

Thanks for the report. Given the streams involved, it sounds like this is going to be using the DRM pipeline and there's an out of memory occurring there. Do you have an estimated amount of time it takes to repro this when watching live events? Also, is it possible to set up a test stream to repro this that is always live? If so, and you don't want to share the link publicly, you can email the email on my bugzilla account and I can keep the link confidential for Mozilla's testing.

Edit: do the errors being thrown show any messages? If so, those would also help narrow down the origin of the OOM in the decoding pipeline.

Flags: needinfo?(dv-web-players+mozilla)
Blocks: media-triage

This has some similarity to bug 1697476.

See Also: → 1697476

Thanks for the response Bryce. I'll email you the test stream and you can access it with any prime account. Based on our previous repro, this happened around 1 hour, 16 minutes into the stream. The only error we see in our log is error contentError: media.error: errorCode: 3. NS_ERROR_OUT_OF_MEMORY (0x8007000e). If we can reproduce this tonight, I'll check the console log to see if we see anything there from the browser.

Flags: needinfo?(dv-web-players+mozilla)
Severity: -- → S2
Priority: -- → P3
Assignee: nobody → bvandyk
No longer blocks: media-triage
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P3 → P2

I'm able to repro this with the test stream. Notes for myself and others as I work through this:

  • I can repro using an official Fx nightly build (after about an hour).
  • I have not been able to repro in a local build (2+ hours of soaking so far).

An important difference between the two builds above is that the official build is served higher resolution video. My working theory is the the OOM is the result of the higher resolution video causes problems. I think the most likely mechanism for this is that we run into internal limits in the shared memory buffers we use for decoding.

Hi, is there any update on this ticket? I know Bryce is out until December 8 but is anyone else able to investigate this until then? We have very high number of users streaming EPL and this is one of the most popular issue we're seeing. Any update would be highly appreciated. Thanks!

A temporary work around may be to force a lower maximum resolution for clients -- it's obviously non-ideal but appears to prevent the OOM.

For Moz folks, I've grabbed logs with

MOZ_LOG=sync,timestamp,GMP:5,EME:5

and didn't see any smoking gun. There's a lot of logs (gigabytes worth), but I expected to see an error in the GMP/EME machinery.

It's possible there's something in there I'm missing, but it may be worth grabbing further logs from the media stack.

What would the maximum resolution limit be for customers in order to avoid this error? We would not be inclined to lower resolution for such a large number of users but want to get an idea on what the trade off would be.

Am back and focusing on this again. The resolution served to non-VMP clients seems to be sufficient to not trigger the issue. Let me see if I can gather some richer logs to trace the source of this.

I've been looking at a similar issue and have further analysis in https://bugzilla.mozilla.org/show_bug.cgi?id=1697476#c27. I'm planning to do more follow up on that bug and will follow up here once I have more info.

I believe this is the same issue as bug 1697476 so am duping against that bug. If the issue still exists in Firefox 99 let me know.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
See Also: 1697476 →

I'm also facing this issue in 103.0b9 .

Possible steps to reproduce:

On Firefox 103.0b9 , Linux x64 , Ubuntu 22.10
Open bilibili.com
Maximize browser window
The window start to flash and console logs:
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
[GFX1-]: IPC Channel is already torn down unexpectedly
[Child 164562, MediaDecoderStateMachine #1] WARNING: Decoder=7f9c3f906a00 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - ProcessDecode: file /build/firefox-8j8MUQ/firefox-103.0b9+build1/dom/media/MediaDecoderStateMachineBase.cpp:151

  • Disabling all addons , themes and plugins doesn't affect this issue.
  • Starting firefox with a new profile won't face this issue.

*Sorry for the delete lines from the version string Firefox 103.b~9

This doesn't occur after disable Use hardware acceleration when available

You need to log in before you can comment on or make changes to this bug.