Ben Nham 1c9127864a Fix nested resource load tracepoints ... https://bugs.webkit.org/show_bug.cgi?id=228242 Reviewed by Alex Christensen. Source/WebCore: The main resource and subresource load tracepoints aren't interpreted correctly if there are multiple resource loads in flight at the same time. To fix this, we pass the pointer to the FrameLoader or SubresourceLoader to ktrace so that the tracing tool can use that pointer to properly nest overlapping resource loading trace intervals. One additional change I made is to move the SubresourceLoadWillStart tracepoint to after the call to willSendRequestInternal. The reason for this is because I wanted to log the resource ID associated with the subresource request, but we only generate that ID after the call to willSendRequestInternal. * loader/FrameLoader.cpp: (WebCore::FrameLoader::provisionalLoadStarted): (WebCore::FrameLoader::checkLoadCompleteForThisFrame): * loader/SubresourceLoader.cpp: (WebCore::SubresourceLoader::willSendRequestInternal): (WebCore::SubresourceLoader::didFinishLoading): (WebCore::SubresourceLoader::didFail): (WebCore::SubresourceLoader::didCancel): Tools: Use page and resource ids to properly handle nested main resource and subresource load tracepoint intervals. * Tracing/SystemTracePoints.plist: Canonical link: https://commits.webkit.org/240400@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@280859 268f45cc-cd09-0410-ab3c-d52691b4dbfc		2021-08-10 18:52:53 +00:00
..
SystemTracePoints.plist	Fix nested resource load tracepoints	2021-08-10 18:52:53 +00:00