Closed
Bug 25910
Opened 25 years ago
Closed 25 years ago
[talkback] random but high hit crash in cache code?
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
CLOSED
FIXED
M14
People
(Reporter: chofmann, Assigned: davidm)
Details
(Keywords: crash, Whiteboard: [PDT+] Must fix 02/25 Have purposed fix ready to check in.)
Attachments
(2 files)
several hits in the m13 talkback reports with a stack that looks like
this.
nsHTTPChannel::~nsHTTPChannel
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPChannel.cpp, line
124]
nsHTTPChannel::`scalar deleting destructor'
nsHTTPChannel::Release
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPChannel.cpp, line
133]
nsCOMPtr_base::~nsCOMPtr_base
[d:\builds\seamonkey\mozilla\xpcom\base\nsCOMPtr.cpp, line 45]
CacheManagerStreamListener::~CacheManagerStreamListener
[d:\builds\seamonkey\mozilla\netwerk\cache\mgr\nsCacheEntryChannel.cpp, line
228]
CacheManagerStreamListener::`scalar deleting destructor'
CacheOutputStream::Release
[d:\builds\seamonkey\mozilla\netwerk\cache\mgr\nsCacheEntryChannel.cpp, line 90]
nsCOMPtr_base::assign_with_AddRef
[d:\builds\seamonkey\mozilla\xpcom\base\nsCOMPtr.cpp, line 54]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsAsyncStreamListener.cpp, line
279]
nsStreamListenerEvent::HandlePLEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsAsyncStreamListener.cpp, line
94]
PL_HandleEvent [plevent.c, line 527]
_md_EventReceiverProc [plevent.c, line 977]
USER32.dll + 0x124c (0x77e7124c)
Reporter | ||
Comment 1•25 years ago
|
||
Reporter | ||
Comment 2•25 years ago
|
||
over to warren?
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/netwerk/protocol/http/src/ns
HTTPChannel.cpp
Assignee: gagan → warren
Summary: [talkback] random but high hit crash in cache code? → [talkback] random but high hit crash in cache code?
Reporter | ||
Comment 3•25 years ago
|
||
any ideas?
Updated•25 years ago
|
Target Milestone: M14
Updated•25 years ago
|
Severity: normal → critical
Has this been seen on Win98 or NT?
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] 2/14/2000
Reporter | ||
Comment 9•25 years ago
|
||
rough look at the data from talkback show that its
exclusively NT bld 1381. how's that for an answer ;-)
attachment update showing platform info to follow in a
minute..
Reporter | ||
Comment 10•25 years ago
|
||
Comment 11•25 years ago
|
||
The talkback incident reports are dead links!
I say change NS_RELEASE(mRequest);
to NS_IF_RELEASE(mRequest);
and call it a day.
Assignee | ||
Comment 12•25 years ago
|
||
sounds good to me.
Assignee: gordon → davidm
Status: ASSIGNED → NEW
Whiteboard: [PDT+] Must fix 02/25 → [PDT+] Must fix 02/25 Have purposed fix ready to check in.
Comment 15•25 years ago
|
||
Arrrrggg!!! This looks like yet another dup of bug #21556.
Assignee | ||
Comment 16•25 years ago
|
||
Marking fixed since someone checked in the code I was going to. As rick says
this is probably a dup.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 17•25 years ago
|
||
Discussed with rpotts. This is apparently a dupe of bug 21556. Closing
and supplying link.
Status: RESOLVED → CLOSED
You need to log in
before you can comment on or make changes to this bug.
Description
•