106562 - Web page causes crash in GKCONTENT.DLL

Status: RESOLVED DUPLICATE of bug 106527

(SeaMonkey :: General, defect)

Description

[jay garcia]

Comment 1

[jay garcia]

Hit enter instead .. sorry

Win98SE 2001102403

URL http://www.nandotimes.com/nation/v-text/story/156731p-1481894c.html causes
crash in GKCONTENT.DLL

Reproducible 100%

Comment 2

[Matthias Versen [:Matti]]

Reporter: 
Can you please use a talkback enabled build and poste the talkback ID in this 
bug ?

Comment 3

[jay garcia]

I've never used a talkback version before. I installed it, visited the site,
crashed, talkback sent. How do I get the Talkback ID to post here??? I did it
twice and didn't see any ID anywhere ...

Comment 4

[jay garcia]

Maybe this is it?? TB37142525X

I searched the directories in the talkback version and came up with the file
INFO.DB and found that number inside. Looks like other ID's I've seen posted here.

Comment 5

[Matthias Versen [:Matti]]

You can get the TB ID if you run 
install-dir\bin\components\talkback.exe

TB37142525X is a valid ID and I hope that this is your crash.

Comment 6

[Asa Dotzler [:asa]]

HTMLContentSink::AddAttributes
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 809]
SinkContext::OpenContainer
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 1494]
HTMLContentSink::OpenContainer
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 3428]
CNavDTD::OpenContainer [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 3455]
CNavDTD::HandleDefaultStartToken
[d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp, line 1304]
CNavDTD::HandleStartToken
[d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp, line 1713]
CNavDTD::HandleToken [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 895]
CNavDTD::BuildModel [d:\builds\seamonkey\mozilla\htmlparser\src\CNavDTD.cpp,
line 526]
nsParser::BuildModel [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 1969]
nsParser::ResumeParse [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 1833]
nsParser::ContinueParsing
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 1485]
HTMLContentSink::ScriptEvaluated
[d:\builds\seamonkey\mozilla\content\html\document\src\nsHTMLContentSink.cpp,
line 5009]
nsScriptLoader::FireScriptEvaluated
[d:\builds\seamonkey\mozilla\content\base\src\nsScriptLoader.cpp, line 527]
nsScriptLoader::ProcessRequest
[d:\builds\seamonkey\mozilla\content\base\src\nsScriptLoader.cpp, line 486]
nsScriptLoader::OnStreamComplete
[d:\builds\seamonkey\mozilla\content\base\src\nsScriptLoader.cpp, line 755]
nsStreamLoader::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamLoader.cpp, line 139]
nsStreamListenerTee::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamListenerTee.cpp, line 25]
nsHttpChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHttpChannel.cpp, line 2326]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 177]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072]
KERNEL32.DLL + 0x24407 (0xbff94407)
0x00688bfe 

Comment 7

[Matthias Versen [:Matti]]

after stack comparing :


*** This bug has been marked as a duplicate of 106527 ***

Comment 8

[jay garcia]

Like I said, this is the first time I've run "talkback", so it has to be the
correct ID as this is the only crash available with the TB version. Now, educate
me, what happens next? with the ID that is.

Comment 9

[Matthias Versen [:Matti]]

I asked the nice Asa on IRC if he can extract the stack trace from your TB ID. 
(only Netscape and Mozilla.org people can do this)
He attached the stack trace from your crash and i found an ealier bug report 
with this crash. (this bug is now closed, you must look into bug 106527)
You can see that this is the same crash if you compare the stack trace in this 
bug with the stack trace in bug 106527.

A stack shows the exact place in the source-code where mozilla crashed.
We can fix a bug if we can reproduce a crash or if you attach a stack trace from 
a debug build (you must compile it yourself) or if you add a talkback ID (the 
nice people from Netscape can extract a stack trace from your TB ID)

Comment 10

[jay garcia]

Thanks, I've been following dev since the very beginning. Looks like I'll keep a
talkback version handy from now on.