Closed Bug 132354 Opened 23 years ago Closed 23 years ago

CPU utilization goes to 100%, browser does not respond

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 121841

People

(Reporter: bashinohed, Assigned: harishd)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031104

When I open this URL: http://www.xml.com/1999/04/holman/xmlcom.msxsl

CPU utilization goes to 100%, browser does not respond

This URL works fine under IE.

Reproducible: Always
Steps to Reproduce:
1. Go to URL http://www.xml.com/1999/04/holman/xmlcom.msxsl
2. CPU utilization goes to 100%
3. browser stops responding

Actual Results:  Browser stops responding
I see it happening on w2k using 2002031803
Status: UNCONFIRMED → NEW
Ever confirmed: true
We are infinite looping at:

nsTextFragment::operator=(const nsAString & {...}) line 142 + 10 bytes
nsGenericDOMDataNode::SetText(nsGenericDOMDataNode * const 0x04803a78, const
nsAString & {...}, int 0x00000000) line 1330
nsGenericDOMDataNode::AppendData(const nsAString & {...}) line 508 + 50 bytes
nsCommentNode::AppendData(nsCommentNode * const 0x04803a94, const nsAString &
{...}) line 60 + 18 bytes
SinkContext::AddComment(const nsIParserNode & {...}) line 1958
HTMLContentSink::AddComment(HTMLContentSink * const 0x0403d070, const
nsIParserNode & {...}) line 3483 + 18 bytes
CNavDTD::HandleCommentToken(CToken * 0x0403c1d0) line 2204 + 34 bytes
CNavDTD::HandleToken(CNavDTD * const 0x040691b8, CToken * 0x0403c1d0, nsIParser
* 0x0403bf30) line 903 + 12 bytes
CNavDTD::BuildModel(CNavDTD * const 0x040691b8, nsIParser * 0x0403bf30,
nsITokenizer * 0x047d6d18, nsITokenObserver * 0x00000000, nsIContentSink *
0x0403d070) line 521 + 20 bytes
nsParser::BuildModel() line 1865 + 34 bytes
nsParser::ResumeParse(int 0x00000001, int 0x00000000, int 0x00000001) line 1731
+ 11 bytes
nsParser::OnDataAvailable(nsParser * const 0x0403bf34, nsIRequest * 0x0402d498,
nsISupports * 0x00000000, nsIInputStream * 0x04035d10, unsigned int 0x00000000,
unsigned int 0x00004000) line 2354 + 21 bytes
nsDocumentOpenInfo::OnDataAvailable(nsDocumentOpenInfo * const 0x0402dec0,
nsIRequest * 0x0402d498, nsISupports * 0x00000000, nsIInputStream * 0x04035d10,
unsigned int 0x00000000, unsigned int 0x00004000) line 241 + 46 bytes
nsHttpChannel::OnDataAvailable(nsHttpChannel * const 0x0402d49c, nsIRequest *
0x0404517c, nsISupports * 0x00000000, nsIInputStream * 0x04035d10, unsigned int
0x00000000, unsigned int 0x00004000) line 2609 + 57 bytes
nsOnDataAvailableEvent::HandleEvent() line 192 + 70 bytes
nsARequestObserverEvent::HandlePLEvent(PLEvent * 0x0404e35c) line 116
PL_HandleEvent(PLEvent * 0x0404e35c) line 590 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x01540f68) line 520 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x002604be, unsigned int 0x0000c14e, unsigned int
0x00000000, long 0x01540f68) line 1071 + 9 bytes
USER32! 77e148dc()
USER32! 77e14aa7()
USER32! 77e266fd()
nsAppShellService::Run(nsAppShellService * const 0x01b45418) line 309
main1(int 0x00000001, char * * 0x00304960, nsISupports * 0x00000000) line 1350 +
32 bytes
main(int 0x00000001, char * * 0x00304960) line 1698 + 37 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77e992a6()

Over to Parser for a look.  Doesn't appear to be an XP Apps bug.  Feel free to
reassign to a more appropriate component.
Assignee: sgehani → harishd
Component: XP Apps → Parser
QA Contact: paw → moied

*** This bug has been marked as a duplicate of 121841 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.