Closed Bug 1497994 Opened 7 years ago Closed 7 years ago

Debug assert with SOCKS5 proxy and TFO

Categories

(Core :: Networking: HTTP, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla65
Tracking Status
firefox65 --- fixed

People

(Reporter: u408661, Assigned: dragana)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

While setting up to look into bug 1493724, I configured a local build (latest mozilla-central as of this morning, no other changes) pointed at the TOR SOCKS5 proxy (127.0.0.1:9150, DNS over SOCKS enabled), and at first page load, I hit the assertion at https://searchfox.org/mozilla-central/rev/80ac71c1c54af788b32e851192dfd2de2ec18e18/netwerk/protocol/http/nsHttpConnectionMgr.cpp#4474. Same thing happened when I restarted the browser after the crash. After disabling tfo, everything is fine. It's not clear to me what the right course here is (should we disable TFO with SOCKS5? should we change the assertion?), nor how urgent of an issue this is, so ni? Dragana, as she's the TFO expert.
Flags: needinfo?(dd.mozilla)
The issue is not really urgent. I could fix this, probably by not trying tfo with socks. I think only if dns over socks is enabled we will hit this assertion.
Flags: needinfo?(dd.mozilla)
Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [necko-triaged]
Keywords: checkin-needed
Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: