1624226 - Virtual memory too low running HTML5

Status: RESOLVED DUPLICATE of bug 1386177

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

Description

[greem_reepo]

Attachment: Capture.PNG

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

Steps to reproduce:

Hello,
What I have discovered with latest legacy Firefox build 56.0.2 (64-bit) and the latest builds of Mozilla Firefox, is that, on Youtube, running HTML5, after a while, all the virtual memory is taken by Firefox.

Actual results:

Firefox did not crash after an add-on was installed that enabled flashplayer on youtube.
Once the add-on was disabled, Firefox crashed within 24h, even if a online radio on YouTube was playing.
This has been tested on Legacy build 56.0.2 (64-bit) and the latest version up to date 64 bit version, on 2 separate machines (only 2 that I have)

Expected results:

Firefox should not crash when the HTML5 player is running.

Comment 1

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

Probably duplicate of very long standing issue in bug #1386177

Comment 2

[Alastor Wu [:alwu]]

I guess that would be fixed by bug 1624711 that solve the memory leak issue on Youtube.

Comment 3

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

It's also reproducible on Firefox 56, so I doubt that it's dupe of bug #1624711.

Comment 4

[Alastor Wu [:alwu]]

Ah, ok, if so I would mark it as P3. But just want to mention that bug 1624711 can help the memory issue on latest Nightly.

Comment 5

[greem_reepo]

It still occurs on the latest version, tested on my laptop, so I had to resort to the FLASH add-on for Youtube.
I still wanted to know a workaround for 56, as upgrading it, will break my legacy plug-ins, add-ons, and custom scripts.

Comment 6

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)