-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Crash when restoring session after Windows/PC boot #4764
Comments
Update: Only seems to happen when shutting down while browser open. |
Experiencing the same thing, only happens on Windows. |
cc: @simonhong Can you take a look? |
|
Recently, c++ adblock lib is replaced with rust based adblock lib - brave/brave-core#2569 |
I've been using the Nightly build (0.69.44) for a few days now. This issue is resolved for me. Nightly is actually more stable than Release for me at the moment because of this issue. |
Thanks for confirming, @Binklebonk! 😄 @Helldembez @chrisknepper - if you're still using Brave and the crash is fairly easy to trigger, can you please try either Nightly or Dev channel and report back? |
I will test it when I have the time. Will report back with the result. |
Tested and found fixed in Version 0.68.100 Chromium: 75.0.3770.100 (Official Build) dev (64-bit) |
Description
When starting Brave after booting the pc the previous session crashes and closes Brave. When starting Brave after the crash it doesn't crash again just lost its session. Happens every time after reboot. This is on a fresh windows 10 install and fresh brave install. Happened before fresh install too.
Steps to Reproduce
Actual result:
Lost session when starting brave after brave crash.
Expected result:
Expecting my previous session without a crash.
Reproduces how often:
So far I've reproduced this multiple times. Basically every time boot my pc.
Brave version (brave://version info)
Version/Channel Information:
Yes
Not tested
Not tested
Not tested
Other Additional Information:
Not tested
Not tested
No
Miscellaneous Information:
2 Crash report ids since fresh windows install.
4073d1d1b8f0aca1
97f08b5aaf72136e
The text was updated successfully, but these errors were encountered: