Skip to content
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

jitstress: BinderTracingTest.ResolutionFlow.cmd failing #85261

Closed
kunalspathak opened this issue Apr 24, 2023 · 3 comments · Fixed by #86180
Closed

jitstress: BinderTracingTest.ResolutionFlow.cmd failing #85261

kunalspathak opened this issue Apr 24, 2023 · 3 comments · Fixed by #86180

Comments

@kunalspathak
Copy link
Member

Failing in jitstress-isas-x86

From the logs, here is the stack trace:

      000000d4`8657b660 00007ffd`6ccebf45 KERNELBASE!RaiseFailFastException+0xae
      000000d4`8657bc30 00007ffd`6cceb7f5 coreclr!_DbgBreakCheck+0x2e5
      000000d4`8657cda0 00007ffd`6cceb9ff coreclr!_DbgBreakCheckNoThrow+0x55
      000000d4`8657ce50 00007ffd`6ce3dfc7 coreclr!DbgAssertDialog+0x1af
      (Inline Function) --------`-------- coreclr!ep_buffer_free+0x20
      (Inline Function) --------`-------- coreclr!buffer_manager_deallocate_buffer+0x57
      000000d4`8657cf70 00007ffd`6ce3e5db coreclr!ep_buffer_manager_deallocate_buffers+0x287
      000000d4`8657d690 00007ffd`6ce47e18 coreclr!ep_buffer_manager_free+0x1b
      000000d4`8657d6c0 00007ffd`6ce3c7bb coreclr!ep_session_free+0xc8
      000000d4`8657d6f0 00007ffd`6ce3bf84 coreclr!disable_holding_lock+0x65b
      000000d4`8657de00 00007ffd`6ce41325 coreclr!disable_helper+0x134
      000000d4`8657def0 00007ffd`6c8e4f3f coreclr!ep_disable+0x165
      000000d4`8657df20 00007ffd`6c8e5ee9 coreclr!EventPipeAdapter::Disable+0xaf
      000000d4`8657dfe0 00007ffd`0d408a31 coreclr!EventPipeInternal_Disable+0xf9
      000000d4`8657e0e0 000001f5`35c0f8b8 0x00007ffd`0d408a31
      000000d4`8657e0e8 000000d4`8657e108 0x000001f5`35c0f8b8
      000000d4`8657e0f0 000001f5`35d23640 0x000000d4`8657e108
      000000d4`8657e0f8 00007ffd`0d40c16e 0x000001f5`35d23640
      000000d4`8657e100 9abcdef0`12345678 0x00007ffd`0d40c16e
      000000d4`8657e108 00007ffd`6d029d28 0x9abcdef0`12345678
      000000d4`8657e110 ffffffff`ffffffff coreclr!vtable_InlinedCallFrame
      000000d4`8657e118 00007ffd`0d76d8b0 0xffffffff`ffffffff
      000000d4`8657e120 000001f5`35d23758 0x00007ffd`0d76d8b0
      000000d4`8657e128 000000d4`8657e0e0 0x000001f5`35d23758
      000000d4`8657e130 00007ffd`0d408a31 0x000000d4`8657e0e0
      000000d4`8657e138 000000d4`8657e1b0 0x00007ffd`0d408a31
      000000d4`8657e140 000001f5`35c0f8b8 0x000000d4`8657e1b0
      000000d4`8657e148 00000000`00000000 0x000001f5`35c0f8b8
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 24, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Apr 24, 2023
@BruceForstall
Copy link
Member

@dotnet/dotnet-diag ?

@hoyosjs hoyosjs added area-Tracing-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 24, 2023
@noahfalk
Copy link
Member

@davmason - that failure callstack looks very similar to another jitstress issue we just peaked at in standup. I don't have that issue number offhand but I think you were looking at it. Potential dupe?

@tommcdon tommcdon added this to the 8.0.0 milestone Apr 25, 2023
@tommcdon tommcdon removed the untriaged New issue has not been triaged by the area owner label Apr 25, 2023
@hoyosjs
Copy link
Member

hoyosjs commented May 1, 2023

Potential dupe of #83575 and #85213

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label May 12, 2023
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label May 15, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jun 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants