Open Bug 1920308 Opened 1 month ago Updated 25 days ago

[toolkit.legacyUserProfileCustomizations.stylesheet] ## Memory leak

Categories

(Core :: Performance, enhancement)

Firefox 130
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: wmwmain, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

When user follows guides such (https://superuser.com/questions/1495946/how-do-i-change-the-background-image-of-home-page-in-firefox) to have an animated gif background on homepage.

I did a lot of research, https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources

Actual results:

That will be causing severe memory leak (100% ram usage after 30min idle with just a few tabs open usually leading to pc crashing). I did everything that (https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources) and countless reddit post's suggest. None of these changes will fix issue.

Expected results:

Memory leak stops immediately after removing gif background by disabling [toolkit.legacyUserProfileCustomizations.stylesheets]. "Disable resource consuming extensions and themes" 'troubleshoot step' should have this preferance option specificy included(!!). Best option would be of course to fix the main issue or maybe develop a new operative way to add gif background in home page of Firefox.

Please capture a profile with http://profiler.firefox.com/, upload it and share the link here.

Component: Untriaged → Performance
Product: Firefox → Core
  1. Please copy-paste teh contents of "about:support" here
  2. When you see the large memory use, please capture a memory report and attach it to this bug. The user guide for capturing memory report can be found here: https://firefox-source-docs.mozilla.org/performance/memory/about_colon_memory.html
Flags: needinfo?(wmwmain)
Blocks: 1923426

Removing perf impact flag and adding to memory investigation meta bu - please continue to provide additional details to help us remedy any possible issues

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