Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 06b5d3e6bd28859e13b589b1bc101905d6fdedaa
https://github.com/WebKit/WebKit/commit/06b5d3e6bd28859e13b589b1bc101905d6fdedaa
Author: Ben Nham <[email protected]>
Date: 2025-09-30 (Tue, 30 Sep 2025)
Changed paths:
M Source/JavaScriptCore/API/JSScriptRef.cpp
M Source/WTF/wtf/SystemTracing.h
M Source/WebCore/page/LocalFrame.cpp
M Source/WebCore/page/UserScript.cpp
M Source/WebCore/page/UserScript.h
Log Message:
-----------
Add trace points for injected bundle and user script evaluation
https://bugs.webkit.org/show_bug.cgi?id=299878
rdar://161662816
Reviewed by Keith Miller.
We are moving more functionality from the injected bundle to WKUserScript. To
help with analyzing
perf traces, we need to add relevant signposts:
- The injected bundle mainly injects scripts via JSScriptRef, so I added
signposts around creating
and evaluating JSScriptRef.
- We already added some user script signposts in 300184@main, but since user
scripts typically carry
no URL, it can be hard to figure out what script is being evaluated. Log the
first line of the
script in the signpost to help with this (up to a limit of 64 characters).
The signpost macros are guarded by a `kdebug_is_enabled` check so we don't do
any of the work
related to the signposts (e.g. getting the debugDescription) unless signposts
are actually enabled.
* Source/JavaScriptCore/API/JSScriptRef.cpp:
* Source/WTF/wtf/SystemTracing.h:
* Source/WebCore/page/LocalFrame.cpp:
(WebCore::LocalFrame::injectUserScriptImmediately):
* Source/WebCore/page/UserScript.cpp:
(WebCore::UserScript::debugDescription const):
* Source/WebCore/page/UserScript.h:
Canonical link: https://commits.webkit.org/300772@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
