[Webkit-unassigned] [Bug 154346] New: Callers of JSString::value() should check for exceptions thereafter.

[bugzilla-daemon at webkit.org]

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

            Bug ID: 154346
           Summary: Callers of JSString::value() should check for
                    exceptions thereafter.
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mark.lam at apple.com

Applying the fix in https://bugs.webkit.org/show_bug.cgi?id=154340 project wide for straightforward cases.

JSString::value() can throw an exception if the JS string is a rope and value() needs to resolve the rope but encounters an OutOfMemory error.  If value() is not able to resolve the rope, it will return a null string (in addition to throwing the exception).  If a caller does not check for exceptions after calling JSString::value(), they may eventually use the returned null string and crash the VM.

The fix is to add all the necessary exception checks, and do the appropriate handling if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160217/85aa35be/attachment.html>