-
Notifications
You must be signed in to change notification settings - Fork 4.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
superpmicollect access violation in pgo Bytemark #76991
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Detailswin-arm64 superpmicollect pgo https://dev.azure.com/dnceng-public/public/_build/results?buildId=49331&view=logs&j=63f2a02a-7891-5505-e9da-45b13105e16b
@dotnet/jit-contrib
|
Unfortunately no symbols there for SUPERPMI-SHIM-COLLECTOR :-( |
If I'm reading the current run logs correctly, those two didn't fail. (could be separate, could seem to be nondeterministic, could be my misreading, etc.) |
I'll investigate. |
Not able to repro this so far. Has it happened repeatedly in CI? |
Ah, I see 6 failures in the past two weeks, including two today. Will keep trying to repro. |
Still no luck with local repro (~50 retries). One of today's failures has a dump file, so will take a look at that. |
As Mark noted, no there are symbols for the collector shim, but from the dump, we can see the entry point was
Not sure why this happens though. |
Actually, it looks like we're trying to read too much from
The last schema entry is
and so the data only extends to So the computation of |
When recording the profile data into the method context, SPMI was assuming all data items were `sizeof(uintptr_t)` which is not guaranteed. Use the proper size. Fixes dotnet#76991.
When recording the profile data into the method context, SPMI was assuming all data items were `sizeof(uintptr_t)` which is not guaranteed. Use the proper size. Fixes #76991.
win-arm64 superpmicollect pgo
(may be broader than pgo - full superpmi collection runs have been failing at times on arm64)
https://dev.azure.com/dnceng-public/public/_build/results?buildId=49331&view=logs&j=63f2a02a-7891-5505-e9da-45b13105e16b
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-bb1a6462f51c458492/JIT.1/1/console.516d02e2.log?helixlogtype=result
@dotnet/jit-contrib
The text was updated successfully, but these errors were encountered: