Bug 2095718
| Summary: | Firefox memory leaks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Ploumistos <alex.ploumistos> | ||||||
| Component: | firefox | Assignee: | Gecko Maintainer <gecko-bugs-nobody> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 36 | CC: | agurenko, bugzilla, erack, gecko-bugs-nobody, jhorak, kai-engert-fedora, klaas, pjasicek, rhughes, rstrode, sandmann, stransky | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | firefox-101.0.1-4.fc36 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-06-16 01:20:54 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Alexander Ploumistos
2022-06-10 11:06:02 UTC
What does say about:memory? Please attach your about:support. Thanks. Also can you test latest mozilla nightly? https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries 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.
Thanks. If you see the regresion on Nightly too it may be from https://bugzilla.mozilla.org/show_bug.cgi?id=1735929 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 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. *** Bug 2095791 has been marked as a duplicate of this bug. *** 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. Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1773953 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! FEDORA-2022-950e0f78c7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-950e0f78c7 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. 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. |