-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Brave is crashing when doing a hard refresh or selecting a new tor connection for this site in the TOR window #23442
Comments
Verified
|
Brave | 1.41.63 Chromium: 103.0.5060.42 (Official Build) nightly (x86_64) |
---|---|
Revision | de0d840bf9439c31bd86bf74f065c31fdf9b208d-refs/branch-heads/5060@{#667} |
OS | macOS Version 12.5 (Build 21G5037d) |
Used the original steps to reproduce.
Confirmed no crashes when obtaining a newly requested Tor IP address
original IP | New Tor connection for this site |
new IP | brave://tor-internals |
brave://tor-internals |
---|---|---|---|---|
Jun 14 17:11:02.781 [notice] Tor 0.4.6.10 running on Darwin with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.12, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Jun 14 17:11:02.781 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 14 17:11:02.781 [notice] Read configuration file "/Users/sdonner/Library/Application Support/BraveSoftware/Brave-Browser-Nightly/cldoidikboihgcjfkhdeidbpclkineef/1.0.25/tor-torrc".
Jun 14 17:11:02.781 [notice] Read configuration file "/Users/sdonner/Library/Application Support/BraveSoftware/Brave-Browser-Nightly/cldoidikboihgcjfkhdeidbpclkineef/1.0.25/tor-torrc".
Jun 14 17:11:02.783 [notice] Opening Socks listener on 127.0.0.1:0
Jun 14 17:11:02.783 [notice] Socks listener listening on port 62851.
Jun 14 17:11:02.783 [notice] Opened Socks listener connection (ready) on 127.0.0.1:62851
Jun 14 17:11:02.783 [notice] Opening Control listener on 127.0.0.1:0
Jun 14 17:11:02.783 [notice] Control listener listening on port 62852.
Jun 14 17:11:02.783 [notice] Opened Control listener connection (ready) on 127.0.0.1:62852
Jun 14 17:11:02.000 [notice] Bootstrapped 0% (starting): Starting
Jun 14 17:11:02.000 [notice] Starting with guard context "default"
Jun 14 17:11:02.000 [notice] New control connection opened from 127.0.0.1.
Jun 14 17:11:02.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Jun 14 17:11:02.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Jun 14 17:11:03.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Jun 14 17:11:03.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Jun 14 17:11:03.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Jun 14 17:11:03.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Jun 14 17:11:03.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Jun 14 17:11:05.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Jun 14 17:11:05.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Jun 14 17:11:05.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Jun 14 17:11:05.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Jun 14 17:11:05.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6854, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Jun 14 17:11:06.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Jun 14 17:11:06.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Jun 14 17:11:07.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
Jun 14 17:11:08.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
Jun 14 17:11:08.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
Jun 14 17:11:08.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Jun 14 17:11:08.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Jun 14 17:11:08.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Jun 14 17:11:09.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Jun 14 17:11:09.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Jun 14 17:11:09.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jun 14 17:11:10.000 [notice] Bootstrapped 100% (done): Done
Marking |
Verification
Used the original steps for testing.
|
This is being uplifted as part of brave/brave-core#13755 and can be verified using |
Verification
Confirmed no crashes when obtaining a newly requested Tor IP address for
|
Verified
|
Verification PASSED on
Went through the STR/Cases outlined via #23442 (comment) and ensured that
|
Description
The issue is reported by @MadhaviSeelam
Brave is crashing when doing a hard refresh or selecting a new tor connection for this site in the TOR window
Steps to Reproduce
check.torproject.org
check.torproject.org
is openedNew Tor connection for this site
in the hamburger menuActual result:
Brave crashes
Expected result:
Should not crash
Reproduces how often:
100%
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @brave/qa-team @rebron @mkarolin @simonhong @emerick
The text was updated successfully, but these errors were encountered: