Firefox has added automatic tab unloading - does this interfere with it?

[gitsjd]

Dev?

[TristanWasTaken]

I just saw the stable release notes. While tab unloads seems more performant than this add-on, the feature still seems to require manually clicking the unload button on tabs.

So instead of asking if it interferes with the add-on, it might be worth to ask if an integration would be possible.

https://support.mozilla.org/en-US/kb/unload-tabs-reduce-memory-usage-firefox

[meeotch]

Just started using this addon. One thing I discovered: if you set browser.tabs.fadeOutUnloadedTabs to True in about:config, you can see that tabs AutoTabDiscard "discards" are also included in the set of tabs Firefox considers "unloaded" (they're greyed out).

@TristanWasTaken - I'm curious what you meant by native FF unloading being "more performant"... Does FF unloading do something more than what ATD accomplishes?

To the OP's question about how the two systems work together: Based on the tab-greying I mentioned above, it looks like tabs that FF has unloaded are not always also discarded by ATD. That is, I still get a mix of grey tabs - some just grey (natively unloaded), and some grey with the "ZZZ" icon (presumably ATD discarded, or possibly both?).

Lastly: I noticed that with ~90 tabs, almost all of which are natively unloaded or ATD discarded, I have 20 Firefox processes in Task Manager. But only 6 of them have the green-leaf "eco mode" badge. I'm curious why that is.

So, for clarity:

1. Is there any reason to prefer one (native unloading vs. ATD) over the other?
2. Is there any reason to disable native FF unloading, and let ATD handle everything?
3. Bonus question: how does this all work with Windows 11 "eco mode" (green leaf icon) for FF processes?

[TristanWasTaken]

I'm curious what you meant by native FF unloading being "more performant"... Does FF unloading do something more than what ATD accomplishes?

@meeotch unloading the tab and removing it from memory seems to be instant for ff native, while this add-on seems to take a while and sometimes doesn't save as much memory as it could, maybe because ff internally directly triggers the flush process and other tasks? Though this could also be caused by unloading many tabs at once.
At least that is how it appears for me.