Open Bug 1554547 Opened 2 years ago Updated 6 months ago

Do not unload WebRTC tabs in low memory situations


(Firefox :: Tabbed Browser, defect, P3)

67 Branch




(Reporter: yoasif, Unassigned)


(Blocks 1 open bug, Regression)


(Keywords: regression, steps-wanted)


User reports that they were on an active Discord call when the tab was unloaded.

I think that users do not expect that active calls should be discarded, even in low memory situations.

Regressed by: 675539

The user claims they had been talking, so in theory this should be covered by tabs with sound playing getting discarded last... unless there were no other tabs to discard?

Keywords: steps-wanted
Priority: -- → P3

If there's a way to detect an active WebRTC session in a tab we can de-prioritize it so that it's less likely to be unloaded. The original use-case for the tabs playing audio assumed "passive" interaction with the tab, e.g. listening to music or something along the lines. An interruption in that case was deemed better than the tab - or Firefox - crashing due to the lack of memory.

Probably, it is better for user to increase the size of swap file in this case. Naturally, it is better to have more RAM but increasing swap file is less problematic.

Also Firefox might give this suggestion to the user about the need to increase the size of swap file or getting more RAM (plus link to Mozilla website showing how to increase the swap file size).

See Also: → 1554990

I've identified a flaw in how we measure low-memory scenarios which might be causing this in bug 1558554.

See Also: → 1558554
Depends on: 1558554
See Also: 1558554
You need to log in before you can comment on or make changes to this bug.