Closed Bug 84495 Opened 23 years ago Closed 23 years ago

Crash in nsHttpChunkedDecoder::ParseChunkRemaining when viewing a mail message

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 82200

People

(Reporter: mscott, Assigned: neeti)

Details

(Keywords: crash)

I'm just randomly browsing through talkback reports for some folks that use the
product regularly. 

I noticed that Phil crashed using the .9.1 build (200106041) with the following
stack trace:

PL_strnchr [../../../../lib/libc/src/strchr.c, line 61]
nsHttpChunkedDecoder::ParseChunkRemaining
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpChunkedDecoder.cpp,
line 84]
nsHttpChunkedDecoder::HandleChunkedContent
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpChunkedDecoder.cpp,
line 55]
nsHttpTransaction::HandleContent
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpTransaction.cpp,
line 477]
nsHttpTransaction::Read
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpTransaction.cpp,
line 718]
nsReadFromInputStream [d:\builds\seamonkey\mozilla\xpcom\io\nsPipe2.cpp, line 831]
nsPipe::nsPipeOutputStream::WriteSegments
[d:\builds\seamonkey\mozilla\xpcom\io\nsPipe2.cpp, line 705]
nsPipe::nsPipeOutputStream::WriteFrom
[d:\builds\seamonkey\mozilla\xpcom\io\nsPipe2.cpp, line 839]
nsReadFromInputStream [d:\builds\seamonkey\mozilla\xpcom\io\nsPipe2.cpp, line 828]
nsHttpTransaction::OnDataReadable
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpTransaction.cpp,
line 218]
nsHttpConnection::OnDataAvailable
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpConnection.cpp,
line 635]

His comment says: reading bug report from naving email

Phil, any chance you can post that email in the bug to help the netwerking folks
track down the crash?
Keywords: crash
One last SPAM, I forgot to put the incident ID: 31362642
I couldn't repro the crash on the same msg next time I launched, which is why I
didn't file a bug.
dup of bug 82200

*** This bug has been marked as a duplicate of 82200 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
VERIFIED:
same problem, from what I can tell.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.