-
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 on opening .onion link #13736
Comments
I'm think this may be related to the issue I created #13723 Are you able to check brave://crashes to see if a report was generated? |
@rkfg I don't it's disabled. I noticed that it's enabled by default but it just doesn't generate a report, though I'm not sure if that means they actually received it or not. I have it enabled but nothing shows up. Check it, it should be toggled under - Help improve Brave's features and performance |
Ok, I enabled it, relaunched the browser and crashed Brave again but there's nothing new on that tab. It doesn't say that reporting is disabled now though. Can you reproduce the crash? Just click that link in the OP with the middle button, should crash instantly. |
Do you have two different types of browser windows open i.e normal or private window along side tor window? Clicking on that link doesn't seem to load. I'm using it via Tor window right now. Every time I've noticed a crash it's always been whenever I've have a separate window alongside tor window. |
I have a normal one with many tabs, when I click the link with the middle button a new window (a private tor window I presume) appears but then both disappear and I see a segfault message in
It's probably a dead site, I found it in Google. But whether it works or not is unrelated as the crash happens on opening this private tor window.
That's the case then I think. I reproduced it in beta and nightly as well, the nightly version doesn't even have any extensions installed and it still crashes like the rest. Might be a Linux-specific issue, idk. |
cc: @darkdh Can you take a look when you get a chance? |
This seems like linux specific, I can't reproduce it on MacOS. Here is the call stack
And it is stuck in a endless loop of |
I'm not sure if it's a different bug but the current tab shouldn't close/crash/disappear when you click an .onion link like it does now. |
Thanks for reporting @rkfg I can easily reproduce the issue on
Steps:
Result: |
@rkfg it is also fixed in the PR |
Verification passed on
Verified test plan from #13736 (comment) Verified test plan from brave/brave-core#7713 |
I know this wasn't reported to be crashing on macOS, but I tested around the issue, just in case, using
Not adding QA Pass-macOS label since I can't reproduce the original problem, though. |
Verification passed on
Verified test plan from #13736 (comment) Verified test plan from brave/brave-core#7713 From brave/brave-core#7713:
|
Description
Brave crashes when you open a second .onion link
Steps to Reproduce
Actual result:
Brave crashes completely (segmentation fault)
Expected result:
The link opens normally
Reproduces how often:
Every single time.
Brave version (brave://version info)
Version/Channel Information:
The text was updated successfully, but these errors were encountered: