Closed Bug 65665 Opened 24 years ago Closed 24 years ago

Why can mTransport be null in AdvanceToNextRequest?

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED INVALID
Milestone:
Future

People

(Reporter: dbaron, Assigned: darin.moz)

Details

Bug 52492 was about crashes in nsHTTPPipelinedRequest::AdvanceToNextRequest caused by mTransport being null. This only happened on some machines. To fix the topcrash, a null check was added. This bug is being written so that you can figure out why it was null (since it should never be), fix it, and remove the null check (leaving the assertion).
Target Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
AdvanceToNextRequest no longer exists in the code base as of the http branch landing. ->INVALID
QA Contact: tever → bbaetz
Code no longer present. VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.