You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Crash in System.Net.WebSockets.Client - Illegal memory access #73621
This is likely the same root cause as #69125. See my comment at #69125 (comment) . You can confirm it by looking at the stacktrace of the crash using unmanaged debugger (lldb, gdb or windbg).
I would expect that any test that depend on sockets is going to hit #69125 with some frequency.
Activity
CarnaViire commentedon Aug 9, 2022
#73222 was merged on 8/5 so it might be related. The product change in the PR is minimal, but it added a bunch of tests.
cc @greenEkatherine
jkotas commentedon Aug 9, 2022
This is likely the same root cause as #69125. See my comment at #69125 (comment) . You can confirm it by looking at the stacktrace of the crash using unmanaged debugger (lldb, gdb or windbg).
I would expect that any test that depend on sockets is going to hit #69125 with some frequency.
wfurt commentedon Aug 9, 2022
I'm looking into it...
hoyosjs commentedon Aug 13, 2022
Seen in https://dev.azure.com/dnceng/public/_build/results?buildId=1941374&view=results, but that stack is the same as #69125
karelz commentedon Aug 15, 2022
Yes, we expect those 2 are dupes -- it was pending verification from @wfurt
wfurt commentedon Aug 22, 2022
There is no failure in
mainsince #73972 was merged.karelz commentedon Aug 23, 2022
Fixed in 8.0 (main) in PR #73972 and in 7.0 (RC1) in PR #74367.