Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#3731 closed defect (invalid)

fetch_from_evbuffer_socks claims to be borken

Reported by: rransom Owned by:
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: bufferevents tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Using Firefox 5.0.1 for Windows with vidalia-bundle-0.2.3.2-alpha-bufferevents-0.3.0-alpha.exe:

Aug 14 03:29:24.498 [Notice] Tor v0.2.3.2-alpha (git-bceb136840815bf5). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows 7  [workstation])
Aug 14 03:29:24.498 [Notice] Read configuration file "C:\Users\rransom\AppData\Roaming\Vidalia\torrc".
Aug 14 03:29:24.498 [Notice] Initialized libevent version 2.0.13-stable using method win32. Good.
Aug 14 03:29:24.498 [Notice] Opening Socks listener on 127.0.0.1:9050
Aug 14 03:29:24.498 [Notice] Opening Control listener on 127.0.0.1:9051
Aug 14 03:29:24.716 [Notice] Based on 100 circuit times, it looks like we don't need to wait so long for circuits to finish. We will now assume a circuit is too slow to use after waiting 4 seconds.
Aug 14 03:29:24.716 [Notice] Parsing GEOIP file C:\Users\rransom\AppData\Roaming\tor\geoip.
Aug 14 03:29:24.934 [Notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Aug 14 03:29:28.117 [Notice] OpenSSL OpenSSL 1.0.0d 8 Feb 2011 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Aug 14 03:29:28.117 [Notice] Reloaded microdescriptor cache.  Found 0 descriptors.
Aug 14 03:29:28.117 [Notice] We now have enough directory information to build circuits.
Aug 14 03:29:28.117 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Aug 14 03:29:28.117 [Notice] New control connection opened.
Aug 14 03:29:28.460 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 2 circuits open. I've pushed 0 kB and received 0 kB.
Aug 14 03:29:29.006 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Aug 14 03:29:31.658 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Aug 14 03:29:32.064 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:29:34.092 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Aug 14 03:29:34.092 [Notice] Bootstrapped 100%: Done.
Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:30:13.871 [Notice] Based on 108 circuit times, it looks like we need to wait longer for circuits to finish. We will now assume a circuit is too slow to use after waiting 5 seconds.
Aug 14 03:30:50.235 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:30:57.052 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:30:57.083 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:30:58.472 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:31:32.792 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:31:42.464 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:31:42.511 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:31:51.419 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:31:52.230 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:35:44.499 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:35:53.703 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:35:53.781 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:39:51.014 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out
Aug 14 03:40:06.286 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to be caught in a parse loop; breaking out

The fetch_from_evbuffer_socks 'Bug' messages are still occurring.

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by nickm

To be clear, is the version really "git-bceb136840815bf5"? The fix for that bug was supposed to be in 553ae5dfb5f6bb4988, which came later.

comment:2 Changed 9 years ago by nickm

Resolution: invalid
Status: newclosed
16:54 < rransom__> nickm, re #3731: I'm running whatever helix packaged in the 
                   0.2.3.2-alpha-bufferevents test bundles for Windows.
16:54 < nickm> ok.  the fix occurred after 0.2.3.2-alpha.
16:54 < rransom__> OK.
16:54 < nickm> may I cut&paste&close?
16:54 < rransom__> Yes.

comment:3 Changed 8 years ago by nickm

Keywords: tor-client added

comment:4 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.