Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 8ff401f233dc9e0c9c9c7aa20b8d6fe945cbbf69
      
https://github.com/WebKit/WebKit/commit/8ff401f233dc9e0c9c9c7aa20b8d6fe945cbbf69
  Author: Alex Christensen <achristen...@apple.com>
  Date:   2025-03-31 (Mon, 31 Mar 2025)

  Changed paths:
    M Source/WebKit/WebProcess/WebPage/WebFrame.cpp

  Log Message:
  -----------
  Make WebFrame destructor assertion more tolerant of WKBundleFrameRef use
https://bugs.webkit.org/show_bug.cgi?id=290765
rdar://142643170

Reviewed by Charlie Wolfe.

A WebFrame is usually constructed, invalidated, then destroyed quite soon.
Use of WKBundleFrameRef can make it so that the destruction of the WebFrame
is delayed for a while, until the last strong reference is dropped.  During
this time, a new WebFrame with the same ID may have been created and registered
with WebProcess::addWebFrame.  If this happens, the assertion just needs to
verify that the currently registered frame is not the frame that is being
destroyed.  It can be null or the next WebFrame.

* Source/WebKit/WebProcess/WebPage/WebFrame.cpp:
(WebKit::WebFrame::~WebFrame):

Canonical link: https://commits.webkit.org/292957@main



To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes

Reply via email to