-
Notifications
You must be signed in to change notification settings - Fork 8
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
Some tabs seem to remain active when there are hundreds of tabs open in a session #1
Comments
Just a guess, but is it because chromium (restores tabs) and (loads extensions) in parallel, as opposed to: waiting for extensions to load/init and then trying to load the tabs... Btw, I'm curious to know more about that, in the hopes to force chromium(by modifying its source code) to wait for extensions to init before attempting any requests or load any tabs. So, if any ideas, please let me know:) EDIT: found all I wanted in my comment below |
Holy smokes! This extensions is god! Thank you for it! EDIT: interesting |
gorhill mentioned:
here: gorhill/uBlock#2067 (comment) EDIT: https://bugs.chromium.org/p/chromium/issues/detail?id=523634 |
@xftroxgpx Ah, that would explain it. Thanks for the hints. Then I guess there is nothing to be done by us.. other than adding a note that "this extension can't prevent all tabs from loading, because of chromium's design." |
I noticed something strange today. Sloth wasn't working in the new Ubuntu install I did until I disabled background running of Chrome. You seeing this? |
I have never enabled background running of Chrome so I don't know. If more people confirm this I can add it as a note in the description. And perhaps we can discuss mitigations. But it should be in a separate issue, me thinks. |
I too never used it, until today when I forgot to change the default. I would've started a new issue but didn't know if this was the issue or anything else I did. If you can confirm this setting causes it you can start a new issue. We will discuss and I will also see what can be done to fix it. |
Using chromium v58
The text was updated successfully, but these errors were encountered: