[Webkit-unassigned] [Bug 195609] New: In CachedFrame's constructor, release-assert that DOMWindow still has a frame after page-caching subframes
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Mar 12 00:05:41 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=195609
Bug ID: 195609
Summary: In CachedFrame's constructor, release-assert that
DOMWindow still has a frame after page-caching
subframes
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: DOM
Assignee: webkit-unassigned at lists.webkit.org
Reporter: rniwa at webkit.org
https://trac.webkit.org/changeset/242677 added release assertions to DOMWindow::suspendForPageCache.
But we still won't be able to tell whether active DOM objects are detaching frames,
or if creating CachedFrame on subframes is causing the frame to go way.
Add a release assertion immediately after creating CachedFrame for subframes to distinguish this case.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190312/13b18c07/attachment.html>
More information about the webkit-unassigned
mailing list