-
-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tabs unloading with the feature disabled #3311
Comments
I found a related discussion that might be helpful: |
It appears that the issue is related to having multiple profiles with different unloader settings, and the setting not being correctly fetched or stored (it can be reproduced when you select "restart later" when changing the setting) |
Hi, @vicky5124. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
The issue is due to conflicting unloader implementations. Tabs in different workspaces are hidden, and hidden tabs get unloaded from memory into disk after a while, which is default Firefox behaviour, behaviour which can be tweaked with extensions such as Tab Stash or Auto Tab Discard (these extensions can be used to solve the issue; install tab stash, configure the extension so it does not unload stashed tabs, and then remove the extension). This default Firefox behaviour overrides the behaviour implemented by the zen browser. |
Hi, does this happen in b.5 / t.6 ? |
I have updated the original message with the versions it happens on |
Alright thanks |
These features are indeed profile-independent. Are you suggesting they shoudn't be or that they dont even work on the same profile? Sorry my english isn't that good |
Captchas
What happened?
When Zen is out of focus (not necessary, but it increases the chances), tabs in deactivated workspaces unload even when the feature is completely disabled.
Below there's a picture of all the relevant configuration entries that should disable unloading entirely, but they only prevent unloading on the active workspace, and keeps unloading tabs in the different workspaces, including pinned tabs that have an increased base weight.
Unloading often happens in the same order displayed in
about:unloads
, but only following the secondary weight (for the most part; it appears to be quite random, but it does mostly follow this metric), which is what allows the pinned tabs to get unloaded, as it is ignoring the base weight that would prevent them from being unloaded.Furthermore, not all tabs in different workspaces get unloaded at once, as most often only a random choice of tabs (regardless of when they were last accessed) get unloaded, including pinned tabs (so, if there are 3 pinned tabs and 20 normal tabs in a workspace, having 1 pinned tab and 12 normal tabs getting unloaded is possible)
Reproducible?
Version
From at least 1.0.1-a.19 to 1.0.2-b.5, including the latest twilight
What platform are you seeing the problem on?
Linux
Relevant log output
No response
The text was updated successfully, but these errors were encountered: