Opened 3 years ago

Closed 3 years ago

Last modified 23 months ago

#17659 closed defect (fixed)

BUG : connection_ap_mark_as_pending_circuit()

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Blocker Keywords: TorCoreTeam201512, 201511-deferred
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Nov 23 [...] [warn] connection_ap_mark_as_pending_circuit(): Bug: What?? pending_entry_connections already contains 0x81b488f8! (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81e10248 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81ab0338 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81a007d8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81b45800 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81e10170 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81b279e8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81d66cb8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81e11558 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x816458a8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x815c11a0 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81d4ddb8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81563fa0 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x81b45f80 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x8129f718 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x814c7350 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x8158c3b0 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 23 [...] [warn] connection_ap_attach_pending(): Bug: 0x819f4a48 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)

Child Tickets

Change History (18)

comment:1 Changed 3 years ago by nickm

Severity: NormalMajor

Were there any earlier warnings of this kind?

Is this a client, a server, a hidden service, or something else?

Any unusual configuration options?

comment:2 Changed 3 years ago by cypherpunks

  • Yes , but only this one :
Nov 21 [..] [warn] connection_ap_attach_pending(): Bug: 0x823ac570 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
  • It's a linux client (normal .. no access trough bridges or anything else )
  • Maybe those ones ?
KeepalivePeriod 60
MaxClientCircuitsPending 128

comment:3 Changed 3 years ago by cypherpunks

Still have other lines in my logs :

Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x822fb260 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x820d05c0 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x82327958 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x824fe848 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x820ab2c0 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x81fde1d8 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x82541500 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_mark_as_pending_circuit(): Bug: What?? pending_entry_connections already contains 0x825bb808! (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x824acb28 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x8265e840 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)
Nov 26 [..] [warn] connection_ap_attach_pending(): Bug: 0x820d0738 is no longer in circuit_wait. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 35bfd782eae29646)

comment:4 Changed 3 years ago by nickm

Keywords: TorCoreTeam201511 added
Severity: MajorBlocker

comment:5 Changed 3 years ago by nickm

Hm. I think I'm going to need a few more log entries to track this down. I've added them in 0c7bfb206ea14ea3115c1b8b214ec79f5e6694e1. Can you reproduce this behavior with the latest master?

comment:6 Changed 3 years ago by cypherpunks

There are also other kinds of warnings :

Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 216 (type 30) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_type_to_string(): Bug: unknown connection type 30 (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x8241b3c0 is no longer in circuit_wait. Its current state is unknown state
[216] on unknown [unknown [30]] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 56 (type 30) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_type_to_string(): Bug: unknown connection type 30 (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x824a6918 is no longer in circuit_wait. Its current state is unknown state
[56] on unknown [unknown [30]] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
...
Nov 27 [..] [warn] connection_ap_mark_as_pending_circuit_(): Bug: What?? pending_entry_connections already contains 0x81f82638! (called from ../src/or/connection_edge.c:1583) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
...
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 206 (type 8) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x824574f0 is no longer in circuit_wait. Its current state is unknown state [206] on unknown [Directory listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 137 (type 11) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x8257cde8 is no longer in circuit_wait. Its current state is unknown state [137] on unknown [Control listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 0 (type 0) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_type_to_string(): Bug: unknown connection type 0 (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x82477e58 is no longer in circuit_wait. Its current state is unknown state [0] on unknown [unknown [0]] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 137 (type 11) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x82362910 is no longer in circuit_wait. Its current state is unknown state [137] on unknown [Control listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 86 (type 16) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x821917b0 is no longer in circuit_wait. Its current state is unknown state [86] on unknown [Extended OR] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 0 (type 4) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x820a7320 is no longer in circuit_wait. Its current state is unknown state [0] on unknown [OR] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 253 (type 6) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x824d5cf8 is no longer in circuit_wait. Its current state is unknown state [253] on unknown [Socks listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 107 (type 25) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_type_to_string(): Bug: unknown connection type 25 (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x82530490 is no longer in circuit_wait. Its current state is unknown state [107] on unknown [unknown [25]] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 211 (type 27) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_type_to_string(): Bug: unknown connection type 27 (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x825f4110 is no longer in circuit_wait. Its current state is unknown state [211] on unknown [unknown [27]] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 98 (type 13) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x81faf238 is no longer in circuit_wait. Its current state is unknown state [98] on unknown [Transparent pf/netfilter listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 46 (type 12) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x820954f8 is no longer in circuit_wait. Its current state is unknown state [46] on unknown [Control] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 137 (type 11) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x8259d610 is no longer in circuit_wait. Its current state is unknown state [137] on unknown [Control listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 137 (type 11) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x81f6cae0 is no longer in circuit_wait. Its current state is unknown state [137] on unknown [Control listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 166 (type 7) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x81836c90 is no longer in circuit_wait. Its current state is unknown state [166] on unknown [Socks] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] conn_state_to_string(): Bug: unknown connection state 137 (type 11) (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x82429740 is no longer in circuit_wait. Its current state is unknown state [137] on unknown [Control listener] connection. Why is it on pending_entry_connections? (on Tor 0.2.8.0-alpha-dev 0c7bfb206ea14ea3)

comment:7 Changed 3 years ago by nickm

oh dear; that looks corrupt. That's a bad sign. I've added another log message to 5665775e8c822d45282d1d56a01a0f5883c7b070.

I've been trying to reproduce this myself, using TorBrowser with a self-built Tor binary on OSX, browsing the web and some hidden services. So far I haven't been able to make it do this. If it's okay to give me some instructions for how I can see this behavior byself, that would be helpful.

comment:8 Changed 3 years ago by nickm

I've gone through the code and added a lot more debugging checks in 0a701e537778ac9da31049f4efebf7cb2bf9c285. This might fix the bug, or might help detect it better. Do things work any better now?

comment:9 Changed 3 years ago by cypherpunks

Steps to reproduce this behaviour :

  • TorBrowser 5.5a4 + tor built from git master
  • (Maybe) Relevant config options
SocksPort 127.0.0.1:9050 IsolateDestAddr IsolateDestPort
KeepalivePeriod 60
MaxClientCircuitsPending 128
  • Open sites with lots of elements (eg. images) coming from the same domain but from hosts with different names

BTW , after testing the latest git master I've obtained only those relevant lines in my logs :

Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x82977108 has impossible magic value 3076712128 (on Tor 0.2.8.0-alpha-dev 0a701e537778ac9d)
Nov 27 [..] [warn] connection_ap_attach_pending(): Bug: 0x829771e0 has impossible magic value 0 (on Tor 0.2.8.0-alpha-dev 0a701e537778ac9d)

comment:10 Changed 3 years ago by nickm

Keywords: TorCoreTeam201512 201511-deferred added; TorCoreTeam201511 removed

Bulk-move uncompleted items to december. :/

comment:11 Changed 3 years ago by teor

I saw this issue happen once in tor master on OS X, but I can't seem to reproduce it.
It seems to be a race condition on connection failure.

I got the following log entries:

[notice] Opening Socks listener on 127.0.0.1:9050
[notice] Bootstrapped 0%: Starting
[notice] Bootstrapped 5%: Connecting to directory server
[warn] connection_ap_attach_pending: Bug: 0x7fa81b519af0 has impossible magic value 2575892462 (on Tor 0.2.8.0-alpha-dev 61430a90b99325b1)

What I did:

  1. Start tor using no arguments: src/or/tor
  2. Block its connections using LittleSnitch (a network interception program that blocks outgoing connections until I make a decision whether to block or allow them)

comment:12 Changed 3 years ago by teor

Oops:
LittleSnitch causes outgoing connections to hang/wait until I make a decision.

comment:13 Changed 3 years ago by cypherpunks

Dec 14 09:26:44.000 [warn] connection_ap_mark_as_pending_circuit_: Bug: What?? pending_entry_connections already contains 0x56245c042410! (called from src/or/connection_edge.c:1608) (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: To debug, this may help.. Stack trace: (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(log_backtrace+0x41) [0x562459ce3c7c] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(connection_ap_mark_as_pending_circuit_+0xd8) [0x562459ca2f69] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(connection_ap_handshake_rewrite_and_attach+0xdc4) [0x562459ca455d] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(connection_ap_rewrite_and_attach_if_allowed+0xa1) [0x562459ca377a] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(connection_edge_process_inbuf+0x498) [0x562459ca1d78] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0xd2af2) [0x562459ca0af2] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(connection_handle_read+0x733) [0x562459c9d445] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x3e207) [0x562459c0c207] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5(+0x1fc59) [0x7f13165e7c59] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5(event_base_loop+0x4a5) [0x7f13165e3d02] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(do_main_loop+0x466) [0x562459c0da38] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(tor_main+0xda) [0x562459c0fb2b] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(main+0x13) [0x562459c0bf43] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(libc_start_main+0xf5) [0x7f131580fb45] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)
Dec 14 09:26:44.000 [warn] Bug: /home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x3de29) [0x562459c0be29] (on Tor 0.2.8.0-alpha-dev a807bb781b2be268)

comment:14 Changed 3 years ago by nickm

a03469a adds more logs to try to figure out why this is happening.

comment:15 Changed 3 years ago by nickm

Status: newneeds_information

I think I got it maybe? #17876 was the root bug here. The commits that fix this bug are, I think:

613e0e1c1ac3e44bad7a876147c49bc232460df2
24fcb6adbb3896395edda38d6ecccb6ad53bddbd

Please let me know if this recurs at any more recent version of Tor. Thanks!

comment:16 Changed 3 years ago by nickm

f1be33fc00484414cffc58e5ba233fa0000838a5 also fixes up some code in this area.

Please let me know if this recurs at any more recent version of Tor than that.

comment:17 Changed 3 years ago by nickm

Resolution: fixed
Status: needs_informationclosed

Haven't heard much on this one in a bit, since I merged the likely fix; calling it fixed!

comment:18 Changed 23 months ago by arma

fyi there are still "#ifdef DEBUGGING_17659", etc lines sprinkled in the source code. Should we take them out?

Note: See TracTickets for help on using tickets.