Closed Bug 1384699 Opened 7 years ago Closed 7 years ago

Crash in mozilla::net::nsHttpChannel::HandleBeginConnectContinue

Categories

(Core :: Networking: HTTP, defect)

Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1363372
Tracking Status
firefox56 --- disabled
firefox57 --- fixed

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-701aa1d4-077d-41c1-882f-219e90170726.
=============================================================

Seen while looking at crash stats - 2 crashes/2 installs on 20170726030207 nightly: http://bit.ly/2uCWsbV
Jason, could you find someone to have a look?

Thanks.
Flags: needinfo?(jduell.mcbugs)
Hi Shane,

It seems that you added nsHttpChannel::HandleBeginConnectContinue() before.

Could you take a look at this crash? Thanks.
Flags: needinfo?(jduell.mcbugs) → needinfo?(mixedpuppy)
The crash stack is very weird because the runnable method has HttpChannelChild in template type but invokes nsHttpChannel function.

>0 	xul.dll 	mozilla::net::nsHttpChannel::HandleBeginConnectContinue()
>1 	xul.dll 	mozilla::detail::RunnableMethodImpl<mozilla::net::HttpChannelChild* const, void ( mozilla::net::HttpChannelChild::*)(void), 0, 0>::Run()
>2 	xul.dll 	nsThread::ProcessNextEvent(bool, bool*)
I don't see why my change from Bug 1360052 would become an issue now since that change landed almost 3 months ago.  Likely something else is causing an issue, but the stack doesn't tell me anything.  Since mayhemer helped me with that patch, maybe he can point us in a direction.
Flags: needinfo?(mixedpuppy) → needinfo?(honzab.moz)
meant to keep my ni
Flags: needinfo?(mixedpuppy)
I think this could be a TFO related crash.  Dragana?
Flags: needinfo?(honzab.moz) → needinfo?(dd.mozilla)
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mixedpuppy)
Flags: needinfo?(dd.mozilla)
Resolution: --- → DUPLICATE
Mark 56 disabled as TCP Fast Open was disabled in 56.
You need to log in before you can comment on or make changes to this bug.