[tbb-bugs] #19921 [Applications/Tor Browser]: TBB 6.5a2: something is going wrong

[Tor Bug Tracker & Wiki]

#19921: TBB 6.5a2: something is going wrong
--------------------------------------+-----------------------------------
 Reporter:  bugzilla                  |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-linkability           |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------

Comment (by bugzilla):

 Well, it was so unexpected that no STR for now.
 But, most likely, it's the same Torbutton's craziness, transformed to a
 new weird behavior.
 In general, some moments were noticed:

 Tor sometimes overloads CPU for 3-4 sec during idle. - related to #19819?

 {{{[08-15 15:47:24] Torbutton INFO: controlPort >> 650 STREAM 489 CLOSED
 69 ip:443 REASON=DESTROY}}} - Is this somehow related to all that
 "getFirstPartyURI failed"?

 {{{[08-15 15:47:27] Torbutton INFO: controlPort >> 250+circuit-status=124
 BUILT 125 BUILT}}} - Where are the other circuits?

 {{{[08-15 15:47:38] Torbutton INFO: controlPort >> 250+circuit-status=124
 BUILT 125 BUILT SOCKS_USERNAME="torproject.org"}}} - How can it be that
 circuit 125 has changed its SOCKS_USERNAME to a new domain?

 {{{Tor NOTICE: Giving up on marked_for_close conn that's been flushing for
 15s (fd 416, type Socks, state open). }}} - What was that?

 {{{[08-15 15:55:41] Torbutton INFO: tor SOCKS:
 https://trac.torproject.org/projects/tor/chrome/common/topbar_gradient.png
 via torproject.org:89e52e1ffbda270503eac23904715f10 getFirstPartyURI
 failed for
 https://trac.torproject.org/projects/tor/chrome/common/topbar_gradient.png:
 0x80070057}}} - Every image started to load twice, some through catchall.

 {{{16:35:08.906 TypeError: Cannot convert string to ByteString because the
 character at index 7722 has value 65279 which is greater than 255.1
 network-monitor.js:387:23}}} - It's the consequence of that mess.

 It was seen for 2 tabs only. The other tabs continued to function properly
 through their circuits.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19921#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online