Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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 unload inactive tabs in firefox?

  • 2 replies
  • 0 have this problem
  • 5 views
  • Paskiausią atsakymą parašė zeroknight

more options

i'm currently writing my own firefox user.js configuration and now i'm at the topic "unloading inactive tabs" like microsoft edge does.

so what are the preferences for this kind of topic?

i want inactive tabs which have not been used for more than 5 minutes to be unloaded.

chatgpt gave me this "browser.tabs.unloadAfterDelay" preference but this one doesn't even exist in the about:config preferenes, would it still work if it doesn't even exist?

i'm currently writing my own firefox user.js configuration and now i'm at the topic "unloading inactive tabs" like microsoft edge does. so what are the preferences for this kind of topic? i want inactive tabs which have not been used for more than 5 minutes to be unloaded. chatgpt gave me this "browser.tabs.unloadAfterDelay" preference but this one doesn't even exist in the about:config preferenes, would it still work if it doesn't even exist?

All Replies (2)

more options

You could look at the following preference in about:config. browser.tabs.min_inactive_duration_before_unload

https://support.mozilla.org/en-US/kb/about-config-editor-firefox

more options

Try the following settings:

browser.tabs.unloadOnLowMemory = true
browser.tabs.min_inactive_duration_before_unload = 300000   (5 minutes in milliseconds)
browser.low_commit_space_threshold_mb = 1000000   (1TB arbitrarily large amount of memory)
browser.low_commit_space_threshold_percent = 100  (Linux-only)


The last two "low commit space" values ensures it always detects a low memory state so it immediately triggers tab unloading after the minimum inactive duration has elapsed. This may have a performance hit though, it causes stuttering for me on Linux if it can't get out of the low memory state. It may work better on Windows.