69478 - Use of illegal syntax ("||" instead of "or") in Xpath expression eats up the whole memory

Status: VERIFIED FIXED

(Core :: XSLT, defect)

Description

[Walter Schmid]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    Standalone XSLT engine, Milestone-18

The following statement in an XSL input file causes the XSLT engine to loop 
until all available memory is used and the CPU usage is up to 100%:
   <xsl:when test = "@type='image/gif' || @type='image/jpeg'">       image.gif 
</xsl:when>
Despite the fact that invalid syntax is used, this error situation should be 
handled in a reasonable way.



Reproducible: Always
Steps to Reproduce:
1.Just let the attached XML- and the XSL-file be input to Mozilla's  standalone 
XSLT-engine and then run it.

Actual Results:  See under bug description

Expected Results:  Correct HTML output. Look at the result, if a logical "OR" 
is used instead of the invalid, C/C++ - like "||" in the expression.

Probably this bug has the same cause as Bug 67004.
The attached example may not be very sophisticated, but it shows the error 
situation very clearly.

Comment 1

[Walter Schmid]

Attachment: XML-input

Comment 2

[Walter Schmid]

Attachment: XSL-input

Comment 3

[Keith Visco]

Error messages need to be reported properly....accepting bug.

Comment 4

[Walter Schmid]

There are no error messages - the system just works until all resources are 
exhausted. Then it stays there. Win2000 reports low virtual memory.

Comment 5

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Fixed with the lexer/parser rewrite

Comment 6

[Axel Hecht]

bitching buttons, verfication spam