-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Force quitting firefox causes saved sessions to fail on next start #1518
Comments
How did you conclude this is a uBO's issue? |
Enabling one add on at a time and re-trying my test case. I have 3 add ons: |
You say
Did you try to answer your own question by trying to reproduce without these rules? |
Yes, opening ublock on the new tab page doesn't allow me to enable/disable the power button. |
Alright, will do this: what you describe is a normal Firefox behavior, nothing to do with uBO. Re-open if and only if you explain very clearly what is actually wrong, along with supporting evidence that uBO is causing whatever you think is wrong. |
I've managed to reproduce the issue already and confirmed it is with ublock. It does not happen in firefox safe mode. I've read your contributing doc and made sure to test this thoroughly |
And it doesn't seem I can reopen github issues: isaacs/github#583 |
You say:
What are you reporting that you think is wrong? When Firefox crashes, this is actually exactly how it is supposed to behave. |
But that behavior doesn't happen in safe mode. Nor did it happen months previously. Recently when starting firefox fresh this page is shown. |
My apologies, Raymond. I resolved the issue by following the steps listed here. https://support.mozilla.org/en-US/questions/956252 |
Force quitting firefox through windows shutdown causes the saved session to fail on next start. Tested with safe mode and exclusively with ublock enabled.
Steps to reproduce:
OS: Windows 7
Browser: Firefox 45.0.1
UBlock: 1.6.6 / Default filter settings
My rules:
Temporary rules
The blank.about rules might be the cause of this?
The text was updated successfully, but these errors were encountered: