[Webkit-unassigned] [Bug 168137] New: StructureStubInfo::considerCaching() should write barrier its owner CodeBlock when buffering a new Structure.

[bugzilla-daemon at webkit.org]

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

            Bug ID: 168137
           Summary: StructureStubInfo::considerCaching() should write
                    barrier its owner CodeBlock when buffering a new
                    Structure.
    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

If we're adding a new structure to StructureStubInfo's bufferedStructures, we should write barrier the StubInfo's owner CodeBlock because that structure may be collected during the next GC.  Write barrier-ing the owner CodeBlock ensures that CodeBlock::finalizeBaselineJITInlineCaches() is called on it during the GC, which, in turn, gives the StructureStubInfo the opportunity to filter out the dead structure.

-- 
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/20170210/e985e04e/attachment-0001.html>