-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[wasm] browser profiler (again) #77779
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
[wasm] browser profiler (again) #77779
Conversation
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis is second attempt to merge #77449 which was reverted. I tested with v8 10.9.130 and V8 10.7.193 and NodeJS v16.13.1.
|
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
wbt failure: |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Failures are unrelated. |
This is second attempt to merge #77449 which was reverted.
On top of previous change I also fix for the different signature on
performance.measureAPI on the V8 and NodeJS shell.I tested with v8 10.9.130 and V8 10.7.193 and NodeJS v16.13.1.