-
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
Browser crash clicking on New private window with Tor #16950
Comments
As we changed some regions(AU, NZ, IE, DE)'s DSE to google, orignally used DDG variants(ex, DDG_DE) was set to initial_id. However, Those regions's default list doesn't have previously used DDG variants. So, |provider_data| could be nullptr. Set DDG always for non QWANT region. fix brave/brave-browser#16950
I wasn't able to reproduce this crash - definitely weird. @stephendonner did you have a particular Country or region set on your computer? |
@bsclifton I was able to reproduce this pretty easily on
Instant crash every single time. I managed to reproduce this using https://github.com/brave/brave-browser/releases/tag/v1.28.85 as well using the same above STR. |
@stephendonner @kjozwiak thanks for the input here! I was able to reproduce also. @simonhong found why it can still crash after you set your region back to US. When the code runs, it will make a call |
…n tor As we changed some regions(AU, NZ, IE, DE)'s DSE to google, orignally used DDG variants(ex, DDG_DE) was set to initial_id. However, Those regions's default list doesn't have previously used DDG variants. So, |provider_data| could be nullptr. Set DDG always for non QWANT region. fix brave/brave-browser#16950
Verification passed on
|
Description
Browser crash clicking on New private window with Tor
Steps to Reproduce
New private window with Tor
Actual result:
Crash: https://share.backtrace.io/api/share/yAMFx3VwjEPrmYPJfX891h3
Expected result:
A new private window with Tor is opened; no crash.
Reproduces how often:
100%
Brave version (brave://version info)
/cc @iefremov
The text was updated successfully, but these errors were encountered: