361180 - 100% cpu usage on certain sites - XML parser messed up

Status: RESOLVED DUPLICATE of bug 360936

(Core :: XML, defect)

Description

[Ronny Perinke]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061110 BonEcho/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061110 BonEcho/2.0

builds before 20061111 work as expected

checkins between 2006-11-10 00:00 and 2006-11-12 00:00
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=AviarySuiteBranchTinderbox&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-11-10&maxdate=2006-11-12&cvsroot=%2Fcvsroot

maybee bug #335047, because xmlparse.c was changed ... but this is just a guess

Reproducible: Always

Steps to Reproduce:
1. update to a build of Firefox 2.0 newer than 20061110 (means at least 20061111)
2. open http://www.sephiroth-j.de/4/index2.php (click refresh, if already visited)
3. you see a 'not well-formed' error
4. change address to http://www.sephiroth-j.de/2/index2.php and press enter


Actual Results:  
Firefox does not respond anymore

Expected Results:  
no errors

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061115 BonEcho/2.0

I can load both sites without any problem.

Comment 2

[Ronny Perinke]

Attachment: picture of one possible XML parsing error using build 2006111503

tested in safe-mode to be sure that the problem is not caused by an extension

Comment 3

[Ronny Perinke]

backing out the changes to xmlparse.c of bug #335047 solved the problem ... 

xmlparse.c diff
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/parser/expat/lib&command=DIFF_FRAMESET&file=xmlparse.c&rev1=1.32.2.2&rev2=1.32.2.3&root=/cvsroot

Comment 4

[Peter Van der Beken [:peterv]]

Can't reproduce this. In the screenshot I see line 52, but the error contains head. Did the testcase change or is the error message/line number messed up?

Comment 5

[Ronny Perinke]

(In reply to comment #4)
> Can't reproduce this. In the screenshot I see line 52, but the error contains
> head. Did the testcase change or is the error message/line number messed up?
> 
The line number is wrong.
I've created a new testcase and I was able to track down the problem. It's caused by the keywords that I am using on this site.

Fx fails with

<meta name="keywords" xml:lang="de" lang="de" content="Sephiroth, Mozilla, Firefox, Bookmarks Menu Button Extension, BMB, Autoclose Bookmark&amp;History Folders, ac-btf, Delete Bookmark Icons, 3DCenter, Winfuture, BBCode, Sephirot" />

Replacing the &amp; by a space character does not help.

Comment 6

[Ronny Perinke]

After further tests I think it's the length of the keywords (or the whole line).

This is ok
<meta name="keywords" xml:lang="de" lang="de" content="Sephiroth, Mozilla, Firefox, Mozilla Firefox, Bug, Bug #361180, XML parser, high cpu usage111" />


But one more character and I get a not well-formed error.
<meta name="keywords" xml:lang="de" lang="de" content="Sephiroth, Mozilla, Firefox, Mozilla Firefox, Bug, Bug #361180, XML parser, high cpu usage1111" />

Comment 7

[Peter Van der Beken [:peterv]]

I still can't reproduce this.

Comment 8

[Ronny Perinke]

I guess I am not alone. :)

http://forums.mozillazine.org/viewtopic.php?t=493191

also happens on http://en.design-noir.de/mozilla/dictionary-switcher/ with Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.1pre) Gecko/20061126 BonEcho/2.0.0.1pre

Comment 9

[Dão Gottwald [:dao]]

I also can't reproduce. Though, given the fact that several users came across this bug, it should be confirmed.

Comment 10

[Szabolcs Horvát]

(In reply to comment #8)
> also happens on http://en.design-noir.de/mozilla/dictionary-switcher/

Unfortunately this website was changed today and now I can not see the error message (tried with the 20061127 and 20061128 builds on WinXP). However I still get reproducible lockups on another site (which unfortunately requires registration and is invitation only so it's no use posting the url here).

Comment 11

[Peter Van der Beken [:peterv]]

I am going to try to write some logging code for the branch, so that we can figure out what is going on here and in bug 360936. It is hard to fix these bugs if I can't reproduce them myself.

Comment 12

[Peter Van der Beken [:peterv]]

Going to mark this duplicate of bug 360936. Please reopen if the problem persists.

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