1577985 - Huge memory usage while playing video with FF 70.0a1 (2019-08-30) (64-bit) on Linux

Status: NEW

(Core :: JavaScript Engine, defect, P5)

Description

[drJeckyll]

Attachment: Screenshot at 2019-08-31 14-01-40.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Play video from f1tv.formula1.com or youtube and RES memory from content process increases while playing. It will be freed if tab is closed, but only will increase while playing.

See attachment for memory usage after one hour video.

Comment 1

[Liviu Seplecan]

Hi @drJeckyll, cannot watch videos from f1tv.formula1.com because I don't have a subscription plan bought. So, please add full info about test the issue or useful TC. I will add a component, if isn't the proper one please fell free to change it. Additionally, please send a full memory report, from about:memory
here are the steps:

1. Wait until Firefox is consuming a large amount of memory
2. In the URL bar type about:memory and press enter
3. Click "Measure and save" (optionally with "anonymize" checked to hide URLs, although this will likely make it more difficult for us to figure out which site, if any, is causing the leak)
4. Save the memory report somewhere
5. Attach the report to this bug

Regards,
Liviu

Comment 2

[drJeckyll]

Attachment: memory-report.json-anon.gz

Comment 3

[Eric Rahm [:erahm]]

Tentatively moving to JS, there's 3GB of ArrayBuffers in that screenshot.

Comment 4

[drJeckyll]

BTW have to say that in google chrome there is no such problem. Attached memory report is from today's FP1 which is hour and a half video - HLS live stream - RES process memory go to more than 5GB. Later watched FP2 which again is hour and a half HLS video stream in chrome and RES process memory sit around 1/2 a gig all the time.

Comment 5

[Jason Orendorff [:jorendorff]]

We would need a login to even begin to look at this.

formula1.com does have contact information that could conceivably put us in touch with a human being:

For TECHNICAL queries related to F1 TV, please email your subscription details to [e-mail]

It still seems like such a long shot, though. -> P3.

I doubt this is really a MemShrink bug. I would guess that Chrome and Firefox are running different code. One way this can happen is if the site e.g. wants to use WritableStream, but falls back on some kind of hacky polyfill if WritableStream isn't natively supported.

Comment 6

[Jason Orendorff [:jorendorff]]

Actually ... drjeckyll, if you could send email to that URL, with your subscription details, and tell them Mozilla's interested in getting in touch with their web developers to understand the problem better, I'd be happy to talk with them.

If you reply, please make sure to check "Request information from:" and enter jorendorff.

Comment 7

[drJeckyll]

I send email to [e-mail]. Let's see what they say (if say anything).

---

Hi there

Thanks for getting in touch. We’ve got your email, and will get back to you in the next 24 hours. If you need to get in touch before then, please quote your reference number (233505).

Need help in the meantime? Check out our FAQs.

Thanks

The Team at F1

Comment 8

[drJeckyll]

Hi there ...,

Thanks for getting in touch with f1 team and for letting us know about this matter.

Our team will be looking into it in order to address this.

If you have any other questions, suggestions or issues, don't hesitate to contact us back.

Hope you'll enjoy the rest of the season!

Kind regards,
Virginia
F1 Team

---

This is the reply I receive from support - hope they take some action

Comment 9

[drJeckyll]

Hi there ...,

We checked your query more closely and we could see that you were using Linux. That might be the cause for the amount of memory used. Please check over here https://f1tv.formula1.com/en/faq that as per our FAQ, we only support the following for the moment:
Desktop
PC - Windows 7 - Chrome
PC - Win 10 - Chrome / Edge
Mac - OSX High Sierra - Safari / Chrome

With any other operating systems and browsers you may encounter difficulties while using the website as they are not yet fully tested and officially supported by our service.

If you have any other questions, suggestions or issues, don't hesitate to contact us back Ognian.

Have an excellent day,
Virginia
F1 Team

---

This is how F1 TV responded

Comment 10

[drJeckyll]

After pressing more I get this reply:

Hi ...,

Thanks for the reply and for being so dedicated regarding the addressing of this problem. We understand your point of view.

We also understand what you mean that the service worked on Linux until now and this problem only occured recently, but this is normal as the Linux operating system is not officially supported yet. Therefore, you may encounter difficulties while using our service on Linux.

We've passed on your request to the developers team, ....

It might take a while for this matter to be processed, so we kindly ask you to have patience as we can't guarantee a time frame for an official update on this. I can assure you however that we're doing everything in our power to address this.

We'll let you know if we have any news.

Kind regards,
Virginia
F1 Team

---

Let's hope somebody from their developers will show up here.

Comment 11

[Liviu Seplecan]

Hi @drJeckyll, due the response from comment 10 I guess you can close this issue and reopen it when you consider - based on when the F1 dev's team decide to handle the problem.
Regards,
Liviu

Comment 12

[Jason Orendorff [:jorendorff]]

Not much we can do right now. Leaving the bug open.

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.