[tor-talk] bug in tor 0.3.4.8?
Hello, I find a load of these bug mentions in the notices log. I run tor-0.3.4.8-0.fc28.x86_64. What now? Sep 15 16:05:03.000 [notice] New control connection opened from 127.0.0.1. Sep 15 16:06:26.000 [warn] tor_bug_occurred_(): Bug: src/or/main.c:1044: conn_close_if_marked: Non-fatal assertion !(connection_is_writing(conn)) failed. (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: Non-fatal assertion !(connection_is_writing(conn)) failed in conn_close_if_marked at src/or/main.c:1044. Stack trace: (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(log_backtrace+0x47) [0x55727ae152e7] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0xbd) [0x55727ae307ad] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(+0x51b18) [0x55727acdbb18] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(+0x235b1) [0x7fb01de555b1] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(event_base_loop+0x537) [0x7fb01de55d47] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(do_main_loop+0x209) [0x55727acde149] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x1015) [0x55727ace0835] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_main+0x3e) [0x55727acd868e] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(main+0x1d) [0x55727acd841d] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libc.so.6(__libc_start_main+0xeb) [0x7fb01c3d611b] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(_start+0x2a) [0x55727acd847a] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] tor_bug_occurred_(): Bug: src/or/main.c:1044: conn_close_if_marked: Non-fatal assertion !(connection_is_writing(conn)) failed. (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: Non-fatal assertion !(connection_is_writing(conn)) failed in conn_close_if_marked at src/or/main.c:1044. Stack trace: (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(log_backtrace+0x47) [0x55727ae152e7] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0xbd) [0x55727ae307ad] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(+0x51b18) [0x55727acdbb18] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(+0x235b1) [0x7fb01de555b1] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(event_base_loop+0x537) [0x7fb01de55d47] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(do_main_loop+0x209) [0x55727acde149] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x1015) [0x55727ace0835] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_main+0x3e) [0x55727acd868e] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(main+0x1d) [0x55727acd841d] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libc.so.6(__libc_start_main+0xeb) [0x7fb01c3d611b] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(_start+0x2a) [0x55727acd847a] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] tor_bug_occurred_(): Bug: src/or/main.c:1044: conn_close_if_marked: Non-fatal assertion !(connection_is_writing(conn)) failed. (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: Non-fatal assertion !(connection_is_writing(conn)) failed in conn_close_if_marked at src/or/main.c:1044. Stack trace: (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(log_backtrace+0x47) [0x55727ae152e7] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0xbd) [0x55727ae307ad] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(+0x51b18) [0x55727acdbb18] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(+0x235b1) [0x7fb01de555b1] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /lib64/libevent-2.1.so.6(event_base_loop+0x537) [0x7fb01de55d47] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(do_main_loop+0x209) [0x55727acde149] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x1015) [0x55727ace0835] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(tor_main+0x3e) [0x55727acd868e] (on Tor 0.3.4.8 da95b91355248ad8) Sep 15 16:06:26.000 [warn] Bug: /usr/bin/tor(main+0x1d) [0x55
Re: [tor-talk] bug in tor 0.3.4.8?
On 15/09/2018 18:14, Udo van den Heuvel wrote: I find a load of these bug mentions in the notices log. It happened again. Any devs reading here? Kind regards, Udo -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] bug in tor 0.3.4.8?
On 17 Sep (15:06:11), Udo van den Heuvel wrote: > On 15/09/2018 18:14, Udo van den Heuvel wrote: > > I find a load of these bug mentions in the notices log. > > It happened again. > Any devs reading here? Hello Udo, I've opened https://trac.torproject.org/projects/tor/ticket/27750 with this problem. Quickly like that, I can't tell you why this is happening or any workaround you could do so keep an eye on the ticket. If this is an 0.3.4.x regression, we'll find it quickly. Thanks! David -- wIa6sCNt07pLMT/73mfGrHDTEF6JdA6MgE2IAeoKcYQ= signature.asc Description: PGP signature -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] bug in tor 0.3.4.8?
On 17/09/2018 17:46, David Goulet wrote: Quickly like that, I can't tell you why this is happening or any workaround you could do so keep an eye on the ticket. If this is an 0.3.4.x regression, we'll find it quickly. Issue is still happening, with just port 22 and 53 open. What can I do to help fix the issue? Udo -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] bug in tor 0.3.4.8?
On Sun, Sep 30, 2018 at 9:48 AM Udo van den Heuvel wrote: > > On 17/09/2018 17:46, David Goulet wrote: > > Quickly like that, I can't tell you why this is happening or any workaround > > you could do so keep an eye on the ticket. If this is an 0.3.4.x regression, > > we'll find it quickly. > > Issue is still happening, with just port 22 and 53 open. > What can I do to help fix the issue? > > Udo If this is easily reproducible, and you can build from source, using "git bisect" to find the first version that caused it would be very helpful. Do you want more info on how to do that? -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] bug in tor 0.3.4.8?
On 06-10-18 01:43, Nick Mathewson wrote: What can I do to help fix the issue? If this is easily reproducible, and you can build from source, using "git bisect" to find the first version that caused it would be very helpful. Do you want more info on how to do that? 0.3.5.3-alpha has an issue very much like the original issue I reported here, despite being patched for that. The OoM situations appear to have been fixed but I need more time to be sure. Udo -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
