Assertion failure: progress <= progressMax (unexpected progress values), at nsHttpChannel.cpp:5465

RESOLVED INCOMPLETE

Status

()

Core
Networking: HTTP
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: dbaron, Assigned: mayhemer)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
I was loading a bugzilla bug in a new tab (I'd just loaded in in an
existing tab with another bug, realized I wanted to keep that tab, gone
back, and opened a new tab).  And I had a tbpl.mozilla.org window open
in another tab, which is what this XMLHttpRequest was clearly associated
with.

I crashed due to:
[5766] WARNING: unexpected progress values - is server exceeding content length?: file /home/dbaron/builds/ssd/mozilla-central/mozilla/netwerk/protocol/http/nsHttpChannel.cpp, line 5304
Assertion failure: progress <= progressMax (unexpected progress values), at /home/dbaron/builds/ssd/mozilla-central/mozilla/netwerk/protocol/http/nsHttpChannel.cpp:5465

(Same assertion as bug 1018883.)

I was running a build from SourceStamp=3c2180b7f1bf
 ... which is my patch queue up to transition-style-rule-followups as of
     Tue Sep 23 14:49:26 2014 -0700, on top of mozilla-central
     revision 9472206fdd12
This Firefox run started at Tue Sep 23 20:18:52 PDT 2014 (uptime 9 days)
(Reporter)

Comment 1

3 years ago
Created attachment 8499071 [details]
gdb session
(Assignee)

Updated

3 years ago
Assignee: nobody → honzab.moz
(Reporter)

Comment 2

3 years ago
Created attachment 8561119 [details]
another gdb session (somewhat different e10s-stack)

... on a build from about a week ago.
can you reproduce this?
(Reporter)

Comment 4

3 years ago
No.  I've posted here every time I've seen it, I believe.
(Assignee)

Comment 5

2 years ago
Seems irreproducible.  Please reopen when happening again.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.