1708822 - TabUnloader.calculateMemoryUsage throws a TypeError exception

Status: RESOLVED FIXED

(Firefox :: Tabbed Browser, defect)

Description

[Toshihito Kikuchi [:toshi]]

TabUnloader.calculateMemoryUsage has a simple mistake, causing TypeError: can't access property "memory", processInfo is undefined when it's executed.

Comment 1

[Toshihito Kikuchi [:toshi]]

Attachment: Bug 1708822 - Handle a case where processMap did not have a corresponding entry. r=NeilDeakin

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/fce297568d02
Handle a case where processMap did not have a corresponding entry.  r=NeilDeakin

Comment 3

[Cristian Brindusan [:cbrindusan]]

https://hg.mozilla.org/mozilla-central/rev/fce297568d02

Comment 4

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

Set release status flags based on info from the regressing bug 1682442

Comment 5

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

The patch landed in nightly and beta is affected.
:toshi, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.

For more information, please visit auto_nag documentation.

Comment 6

[Toshihito Kikuchi [:toshi]]

TabUnloader is disabled by default. To hit this bug, a user needs to enable this feature through the pref and to have a low-memory situation with more than 10 inactive tabs. Even if they hit the issue, a symptom is that tabs are not unloaded. Setting the status to wontfix.