Closed Bug 166709 Opened 22 years ago Closed 22 years ago

Parsing crashes [@ nsParser::WillBuildModel]

Categories

(Core :: DOM: HTML Parser, defect)

x86
All
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: greer, Assigned: harishd)

Details

(Keywords: crash, topcrash)

Crash Data

N700 (Gecko1.0) and M110 (MozillaTrunk) Talkback data is showing a combined 60
crashes at the signature nsParser::WillBuildModel. Over to parser for first
look. Could this be a mishandling of the data following the stop request?

Stack Trace: 

	 nsParser::WillBuildModel
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp  line 1236]
	 nsParser::ResumeParse	[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp
 line 1717]
	 nsParser::OnStopRequest
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp  line 2416]
	 nsDocumentOpenInfo::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp  line 256]
	 nsStreamListenerTee::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamListenerTee.cpp  line 66]
	 nsHttpChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpChannel.cpp  line 2901]
	 nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp  line 213]
	 PL_HandleEvent	[d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c  line 597]
	 PL_ProcessPendingEvents	[d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c 
line 530]
	 nsEventQueueImpl::ProcessPendingEvents
[d:\builds\seamonkey\mozilla\xpcom\threads\nsEventQueue.cpp  line 392]
Keywords: crash, topcrash
Tom: Could you provide me with a url or a testcase to reproduce the problem? 
No current incidents in the database.  All occurances are from 2002 builds. 
Marking fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Crash Signature: [@ nsParser::WillBuildModel]
You need to log in before you can comment on or make changes to this bug.