1591381 - Memory leak when opening Settings in 71.0b3

Status: RESOLVED WORKSFORME

(Firefox :: Settings UI, defect)

Description

[George Thomas]

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

Steps to reproduce:

Installed Firefox Beta 71.3 on Windows 10
Open Settings (in Firefox)
Monitor Ram usage in Windows Task Manager
One Firefox process continues to grow in memory usage until the browser becomes completely unresponsive.

Actual results:

Firefox becomes unresponsive and memory usage spikes, until force closed or crash

Expected results:

No memory spike/leak to occur when opening settings page

Comment 1

[George Thomas]

Attachment: Screenshot.png

Screenshot showing process and unresponsive firefox after opening the settings page

Comment 2

[George Thomas]

Attachment: troubleshooting information.txt

Copy paste of Troubleshooting information (might be useful)

Comment 3

[:Gijs (he/him)]

Does the same thing happen in Firefox's safe mode ( https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode ) or a clean profile ( https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles ) ?

Does the browser ever recover (ie are you able to interact with it if you wait a while) ?

Comment 4

[George Thomas]

Same thing happens in safe mode. Haven't tried a clean profile. The browser does not recover. As soon as the settings or options page is opened the ram usage keeps increasing until the browser crashes. The browser is usable as long as the options page is not opened.

I updated to beta 4 and the issue seems to be resolved. Not sure why or what was changed.

Comment 5

[:Gijs (he/him)]

Worksforme given this has gone away, I guess, though I'm still not sure what would have caused this. Not much changed between beta 3 and 4: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_71_0b3_BUILD1&tochange=FIREFOX_71_0b4_BUILD1 and nothing jumps out at me as something that would really explain this... mysterious!

Do let us know if this recurs.