-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Contract violation in GC Profiler test #67630
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
This looks like the primary issue is a null reference somewhere in the call chain of the ProfToEEInterfaceImpl::GetObjectGeneration, which results in a vectored exception handler being called and doing its stuff. So it is not a problem of the contract itself, as an access violation exception is not expected to happen in native runtime code. |
Here is the full stack trace:
The frame 0x1c is attempting to access memory at
|
Tagging subscribers to this area: @dotnet/gc Issue Details
|
Failed again in #67823 |
@cshung anything which has been recently fixed for this? |
I did some investigation of this but I haven't nailed the root cause yet. One thing for sure is that the pointers returned by the second parameter of the In a typical scenario, I confirm that the object reported by this API matches exactly with what |
Failed again in: runtime-coreclr jitstress-isas-x86 20220521.1 Failed test:
Error message:
|
In https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-67599-merge-26eaddf607184fe28a/profiler.gc/1/console.82d7f3ce.log?sv=2019-07-07&se=2022-04-25T18%3A57%3A26Z&sr=c&sp=rl&sig=wd65GZnAyydb6efKQdfc0TtHGmIGeTWwgyU5S255L9M%3D
The text was updated successfully, but these errors were encountered: