-
Notifications
You must be signed in to change notification settings - Fork 5k
[browser] EP profiler - identify top frame, positive PID #115825
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses several profiler and event tracing issues by ensuring proper PID values and refining profiler call handling for improved stability and API consistency.
- Update WASM sample project instrumentation configuration
- Ensure interpreter frames correctly set the instruction pointer prior to profiler callbacks
- Update event tracing calls and diagnostics promises to resolve profiler-related issues
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
src/mono/sample/wasm/browser-eventpipe/Wasm.Browser.EventPipe.Sample.csproj | Updated instrumentation configuration for WebAssembly profiling |
src/mono/mono/mini/interp/interp.c | Modified profiler call blocks to set the instruction pointer correctly |
src/mono/mono/eventpipe/ep-rt-mono-runtime-provider.c | Adjusted event writing to pass the correct thread context and updated context initialization |
src/mono/browser/runtime/startup.ts | Updated PID calculation to produce a positive 31-bit integer |
src/mono/browser/runtime/diagnostics/diagnostics-js.ts | Added resolution of onClosePromise after diagnostic client closure |
/backport to release/10.0-preview5 |
Started backporting to release/10.0-preview5: https://github.com/dotnet/runtime/actions/runs/15192146608 |
module <<?!?>>
in perfView for methods on top of the stack