[Webkit-unassigned] [Bug 55479] New: Begin Characters Optimization Causes YARR Interpreter Errors

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=55479

           Summary: Begin Characters Optimization Causes YARR Interpreter
                    Errors
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
               URL: http://www.sirensclef.com/webkit/tinymce/
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: msaboff at apple.com


This issue was found while investigating https://bugs.webkit.org/show_bug.cgi?id=54978.

The temporary resolution to that defect was to disable the setting up of the begin characters optimization.

It appears that the begin characters code is not properly setting up the data.  From the original bug, it appears that the regular expression:
    /<((\/([^>]+)>)|(([^>]+)>))/
correctly finds '<p>' from the string '<p>This content should not appear as HTML <strong>source</strong>.</p>' when run via the interpreter.  If one adds (ABC>) as an alternative to the regular expression:
    /<((ABC>)|(\/([^>]+)>)|(([^>]+)>))/
then the interpreter doesn't find '<p>' in the subject string.

Walking through the code, the setupBeginChars() method determines that the first expression (w/o the (ABC>)) is not a candidate for the begin characters optimization.  The setupBeginChars() determines that the second expression is a candidate for the begin characters optimization and it looks for the strings "<A" and "</" which come from the first two alternatives. The last alternative isn't included in the optimization strings.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.