Closed Bug 1553633 Opened 6 years ago Closed 6 years ago

Memory leak when opening about:preferences

Categories

(Firefox :: Settings UI, defect)

68 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: Tobias.Marty, Unassigned)

Details

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

Steps to reproduce:

Updated Firefox to 68 Beta 3 (with German language pack). Opened about:preferences.

Actual results:

Massive memory leak which makes the browser unresponsive until killing it with Windows task manager.
It works in safe mode. Only two addons active are Firefox Pioneer and uBlock Origin. Disabling uBlock Origin in normal mode still causes memory leak.

Component: Untriaged → Preferences

As the memory begins to reach its limits, would you be able to go to about:memory, and click "Measure and save" to save a memory report, and then post it in this bug? That might help us track down what's eating your memory here.

Flags: needinfo?(Tobias.Marty)

It stays at about 3 GB memory used with a total of 8 GB system RAM. CPU usage is very high, but I tried to save a report. Here's a link: https://1drv.ms/u/s!ArY6nA0dfc6ug5JKFT0CvNHgeHyXWQ

Flags: needinfo?(Tobias.Marty)

Wow, 4.5GB in heap-unclassified there.

Hey mccr8, in bug 1436220, erahm gave some pretty detailed instructions on how to get a DMD build running and emitting useful information on Linux-y machines. Do you know if there are similar instructions for Windows users?

Flags: needinfo?(continuation)

Probably not written up so nicely. https://developer.mozilla.org/en-US/docs/Mozilla/Performance/DMD has some information scattered around.

Flags: needinfo?(continuation)

I found the cause. After using an English installer to manually update Firefox I downloaded a German language pack with the according menu options. After using a German installer and removing the German language pack and dictionary with about:addons the memory leak is gone.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.