We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to find which extension has a memory leak?

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 8 views
  • Last reply by user633449

Hello! I have a few addons(extensions) and I think that one of them has a memory leak. I can say that because in the "about:memory" tab the WebExtension process can eat all of my free memory (see the attached screenshot). And after that Firefox usually crashes. Example crash report: https://crash-stats.mozilla.com/report/index/97e8dba8-c749-42d3-bfb2-865fd0180307

Is it possible to find out which addon is responsible for huge memory allocations? For example, Chrome has very good "Task Manager" window where you can see "Memory footprint" for each extension and tab. Does the Firefox has the similar functionality somewhere?

Hello! I have a few addons(extensions) and I think that one of them has a memory leak. I can say that because in the "about:memory" tab the WebExtension process can eat all of my free memory (see the attached screenshot). And after that Firefox usually crashes. Example crash report: https://crash-stats.mozilla.com/report/index/97e8dba8-c749-42d3-bfb2-865fd0180307 Is it possible to find out which addon is responsible for huge memory allocations? For example, Chrome has very good "Task Manager" window where you can see "Memory footprint" for each extension and tab. Does the Firefox has the similar functionality somewhere?
Attached screenshots

All Replies (1)

Enable one extension at a time to find the issue