Bug 2095718 - Firefox memory leaks
Summary: Firefox memory leaks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 36
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2095791 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-10 11:06 UTC by Alexander Ploumistos
Modified: 2022-06-16 01:20 UTC (History)
12 users (show)

Fixed In Version: firefox-101.0.1-4.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 01:20:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
about:support and about:memory reports (682.07 KB, application/x-xz)
2022-06-10 12:32 UTC, Alexander Ploumistos
no flags Details
memory reports before and after running the aquarium demo (187.52 KB, application/x-xz)
2022-06-11 20:21 UTC, Alexander Ploumistos
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1773953 0 -- NEW Crash taking down Nightly and the terminal tab it was opened from when using route mapping websites 2022-06-13 09:34:27 UTC

Description Alexander Ploumistos 2022-06-10 11:06:02 UTC
Starting with build version 101.0-2.fc36 I get memory leaks when browsing multimedia-heavy sites. Killing tabs from the integrated task manager doesn't help, I have to restart Firefox.

I tested firefox-101.0.1-1.fc36 and also Mozilla's 101.0.1 binary with clean profiles. There were no issues with the latter.

The quickest reproducer I found was logging into hero-wars.com (requires login) and within seconds, all the RAM fills up.

There are no issues with firefox-101.0-1.fc36.

Intel graphics, x11 session.

Comment 1 Martin Stransky 2022-06-10 11:31:53 UTC
What does say about:memory? Please attach your about:support.
Thanks.

Comment 2 Martin Stransky 2022-06-10 11:34:46 UTC
Also can you test latest mozilla nightly?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries

Comment 3 Alexander Ploumistos 2022-06-10 12:32:59 UTC
Created attachment 1888663 [details]
about:support and about:memory reports

I did three tests: one with firefox-101.0.1-1.fc36, one with Mozilla's 101.0.1 and a third one with the 103.0a1 Nightly.

I have included the about:support info from all three and the memory reports before loading the game and after letting it run for a few minutes - I hope they are useful. If you need something more concise, please let me know what.

I hit the same issue with the Nightly.

Comment 4 Martin Stransky 2022-06-10 12:36:13 UTC
Thanks. If you see the regresion on Nightly too it may be from https://bugzilla.mozilla.org/show_bug.cgi?id=1735929

Comment 5 Chris Murphy 2022-06-10 18:23:54 UTC
Might be nice to find an example that doesn't require a login (I've got the same problem, my reproducer is a zoom session so that requires two people to reproduce).

This is probably a dup of bug 2095791

Comment 6 Martin Stransky 2022-06-11 19:52:39 UTC
Can you try a general WebGL example from https://webglsamples.org/ ? For instance https://webglsamples.org/aquarium/aquarium.html or https://webglsamples.org/blob/blob.html ?
Thanks.

Comment 7 Martin Stransky 2022-06-11 19:52:58 UTC
*** Bug 2095791 has been marked as a duplicate of this bug. ***

Comment 8 Alexander Ploumistos 2022-06-11 20:21:19 UTC
Created attachment 1889005 [details]
memory reports before and after running the aquarium demo

(In reply to Martin Stransky from comment #6)
> Can you try a general WebGL example from https://webglsamples.org/ ? For
> instance https://webglsamples.org/aquarium/aquarium.html or
> https://webglsamples.org/blob/blob.html ?
> Thanks.

It takes a bit longer, but it happens. With 101.0-1 memory usage remains constant after loading the aquarium demo, whereas with 101.0.1-1 it increases linearly.
I've uploaded the memory reports of the run with 101.0.1-1, just in case.

Comment 9 Martin Stransky 2022-06-13 09:16:02 UTC
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1773953

Comment 10 Alexander Ploumistos 2022-06-14 20:40:53 UTC
Running 101.0.1-4 I can no longer reproduce the issue, feel free to add this bug to bodhi when you create the update.

Thanks a lot Martin!

Comment 11 Fedora Update System 2022-06-14 21:18:00 UTC
FEDORA-2022-950e0f78c7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-950e0f78c7

Comment 12 Fedora Update System 2022-06-15 01:11:05 UTC
FEDORA-2022-950e0f78c7 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-950e0f78c7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-950e0f78c7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2022-06-16 01:20:54 UTC
FEDORA-2022-950e0f78c7 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.