-
Notifications
You must be signed in to change notification settings - Fork 79
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
[Ubuntu/Firefox Beta 106] Auto Discard Stopped Working #310
Comments
I performed a few experiments:
None of these fixed my issue. I know for a fact v0.5 was working fine. This appears to be an issue specific to Firefox v106 beta and Ubuntu v22.04. |
I am having the same issue on Firefox Developer (same build v106.0b3 64-bit) on Windows 11. The only changes I'm aware of that was made to my system when the issue occurred was browser update. |
OK I actually have v0.5.0 working. For some reason I had to close the browser and reopen it after installing that version of the addon. @Thereatra perhaps this will help you in the meantime until the current version is fixed. |
After catching issue #307, the downgraded 0.5.0 worked fine. Edit: |
Firefox has activated |
Thanks for looking into this! To help others in this thread, here's how you can test it.
At this point, you should be running the test add-on for this session. I haven't gotten there yet, but I believe everything is reverted once the browser closes. @rNeomy It is working for me (Firefox v106.0b9, Ubuntu v22.04 64-bit)! Thank you so much! |
It works well for me, too. Thank you. |
Sorry for the very late reply, I've been away for a bit. The test file worked fine for me too! Any ideas when this may be pushed to Firefox addons? Thanks. |
Also FYI Firefox v106 goes stable/public release today. |
Version |
Auto (time-based) discard has stopped working. Tabs are not auto discarding when the time (5 min exceeding 1 inactive tab in my setup) is hit. It looks like this is related to the v0.6.3.2 release I received Sep 24, however Firefox v106 came out this week and it might be related to that as well. I don't have a firm grasp of when this broke. I'm only certain that it happened within the past few days. I'm running Firefox v106.0b3 64-bit on Ubuntu 22.04. Other than Firefox updating to 106 beta, my setup has remained fairly static.
The text was updated successfully, but these errors were encountered: