-
Notifications
You must be signed in to change notification settings - Fork 15.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: enable Perfetto in Chromium #41880
Conversation
@nornagon i'm observing with Perfetto enabled that this test passes even when I delete the entirety of |
That test looks pretty solid to me, so I'd trust the results. It looks like most of TracingControllerImpl is not compiled when perfetto is enabled, so it makes sense that deleting it wouldn't have any effect when perfetto is enabled. [EDIT]: oh, whoops, I see you linked to the version of the file in this PR which adds the #ifdef. But still, the test is fairly strong so I think we're okay to trust it. |
01d6fec
to
efa3ee7
Compare
53fd714
to
ff3258f
Compare
ff3258f
to
b5bb543
Compare
No Release Notes |
I have automatically backported this PR to "31-x-y", please check out #41910 |
Description of Change
Enable perfetto with Node.js and turn off
use_perfetto_client_library = False
. Node.js disables perfetto by default but is broken on build - they don't currently add guards forV8_USE_PERFETTO
and upstream only defines certain functions (ex.GetCategoryGroupEnabled
)onv8::TracingController
if perfetto is disabled. Electron already had minimal to no support for Node.js trace events, so the impact of adding associated guards there should be relatively small.Checklist
npm test
passesRelease Notes
Notes: none