Closed Bug 1369205 Opened 7 years ago Closed 7 years ago

Crash in @0x0 | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::OnTransportStatus

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Version:
55 Branch
Platform:
x86
Windows 10
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla56
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox55 --- disabled
firefox56 --- fixed

People

(Reporter: marcia, Assigned: dragana)

Details

(Keywords: crash, Whiteboard: [necko-active])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-0937d773-eae1-4bb0-aa90-73d360170531.
=============================================================

Seen while looking at crash stats - so far 5 crashes/1 install: http://bit.ly/2sowvud

Probably related to turning TFO on again?
assigning to me, I will take a look tomorrow.

Thanks Marcia!
Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Crash Signature: [@ @0x0 | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::OnTransportStatus] → [@ @0x0 | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::OnTransportStatus] [@ PLDHashTable::Search | nsClassHashtable<T>::Get | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::FindTransactionHelper ]
Whiteboard: [necko-active]
Signature @0x0 | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::OnTransportStatus has been fixed by bug 1369509.

Signature @ PLDHashTable::Search | nsClassHashtable<T>::Get | mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::FindTransactionHelper ] has been mostly fixed by bug 1369509. The volume is reduce from from 40 per buildId to only 1. This single crash can be part of our latent bug in nsHttpConnectionMgr.

I will keep this open for observation.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
status-firefox55: affected → disabled
status-firefox56: --- → fixed
status-firefox-esr52: --- → unaffected
Target Milestone: --- → mozilla56
You need to log in before you can comment on or make changes to this bug.