If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Firefox crashes due to allocating maximum memory (2.2GB+) after switching resolutions in Youtube video player

RESOLVED WORKSFORME

Status

()

Firefox
Untriaged
RESOLVED WORKSFORME
5 years ago
4 years ago

People

(Reporter: Marius Hudea, Unassigned)

Tracking

({stackwanted})

13 Branch
x86_64
Windows 7
stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Build ID: 20120614114901

Steps to reproduce:

This is a constant issue in the last days, but has happened randomly at other times in the past. 
My current isp seems to have some issues with their caching servers or whatever they do, so this issue appears almost on a daily basis now.

Basically when I watch a video on Youtube, it starts by default at 360p or 480p and the player buffers up to a point and then it stops. This point is random, sometimes it's 10 minutes within a video, other times it's 20-30 minutes in it.

When the playback reaches that point, invariably Youtube's player fails to reconnect to the stream so I'm forced to select another resolution from the bottom right corner of the player. This works every time - Youtube picks another download location and finishes the stream at the higher resolution.

Probably every 6-10 videos I watch in a session, the moment the video transfer starts, the main firefox process memory increases, as if the whole video is kept in its memory. 
With 30-40 minutes at 720p or 1080i/p, this is enough for the firefox process to reach over 2 GB of memory. 

The other processes, plugincontainer and flashplayer show normal memory usages 10-60 MB of memory.

In some cases, I can predict firefox will crash by hearing the hard drive starting to swap a lot (the system only has 4 GB of memory installed) so by killing plugincontainer or Flashplayer I can make Firefox recover (the page will say the plugin has crashed) and memory decreases back to normal values (200-400 MB).


Actual results:


watching sd stream on Youtube, times out after a while, switching to a HD resolution resumes stream.
Not always but often enough to be annoying, firefox.exe's memory consumption increases in tandem with the actual new stream's transfer speed, until firefox crashes due to using over 2 GB of memory. 


Expected results:

Firefox shouldn't start using memory all of the sudden, should fail more gracefully. 
At the very least a 64bit version should be made available to alleviate this issue

Comment 1

5 years ago
Can you provide the two crash IDs (bp-...) from about:crashes?
Does it happen with a new profile (see http://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles)?
(Reporter)

Comment 2

5 years ago
Thank you for answering so fast.

Last time it happened today, Firefox did report that it crashed and asked me to submit information... I filled in some details and clicked submit but it said an error occurred and it couldn't submit. 
Also, I remember I tried to click Details and it didn't do anything.

about:crashes list the last id as bp-efd02c9a-0efc-4f73-adb2-a9c302120710 

I'll try to replicate it both in current profile and a new one, and I'll also try to click on "Stop download" in the Youtube flash player before the 2 GB of memory is reached, so that I may potentially be able to use about:memory and upload here what it says.

Other suggestions are welcome.

Comment 3

5 years ago
(In reply to Marius Hudea from comment #2)
> about:crashes list the last id as bp-efd02c9a-0efc-4f73-adb2-a9c302120710 
This one has a corrupt dump, so not useful for Mozilla.
If you hit again this kind of crash signature, try to generate a valid stack trace differently: https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

You should update your graphic drivers that has some vulnerabilities:
http://support.amd.com/us/kbarticles/Pages/catalyst126legacyproducts.aspx

If you have info concerning about:memory, please provide it as an attachment to this bug.
Keywords: stackwanted
(Reporter)

Comment 4

5 years ago
I can not reproduce this issue with a clean profile.
With the old profile, the highest memory consumption I managed was about 2 GB, so I was unable to make it crash. 

Basically, it's just an issue of being "lucky" enough to get a long video AND have this issue appear, because memory usually goes down the moment the video is fully buffered by the Youtube player.

Right now, I could only do an about:memory dump when the memory was at about 1.7GB ... I'll attach it but as far as I can see I doubt it's useful. When it was close to 2 GB I tried to do the about:memory page, clicked on More verbose, Firefox complained about the script not responding about 3-4 times but by the time it was finished crunching data the video transfer finished and memory went down to about 400 megs.

This profile has the following addons installed : Firebug + Google Page Speed, Live HTTP Headers, Flashblock (disabled for Youtube), RefControl, Status4Ever, Lazarus Form Recovery.

I suspect it might be Firebug trying to cache the contents in memory, to show it in the Net tab if user clicks on one of those URLs. But I don't have any proof.

I'll keep trying to crash it, if I do manage a successful crash report, I'll post the ID from about:crashes

Currently it's a bit hard for me to try nightly builds, so not sure if I'll be able to do traces with WinDbg.
The AMD drivers are the latest for this video card (Radeon 4850) and video acceleration is disabled in both Firefox and Flash.

Thanks again for your help.
(Reporter)

Comment 5

5 years ago
Created attachment 641026 [details]
memory usage, about 1.7 GB

memory usage, about 1.7 GB
If still fails with a recent version please reopen
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.