-
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
Crash in System.Net.WebSockets.Client - Illegal memory access #73621
Comments
Tagging subscribers to this area: @dotnet/ncl Issue Details8/9:
Failures are on Linux only, with mix of architectures - arm64, amd64. Regression started on 8/5. 2 notable failures are on Rolling runs: let crashes = (friendlyNamePrefix : string, includePR : bool) {
cluster('engsrvprod.kusto.windows.net').database('engineeringdata').WorkItems
| where FriendlyName startswith friendlyNamePrefix
//| where Queued > ago(7d)
| where Status == "BadExit"
| where ExitCode == 139
| join kind=inner (cluster('engsrvprod.kusto.windows.net').database('engineeringdata').Jobs
| where ((Branch == 'refs/heads/main') or (Branch == 'refs/heads/master') or (includePR and (Source startswith "pr/")) or (Branch startswith 'refs/heads/release/6.0'))
| where Type startswith "test/functional/cli/"
and not(Properties contains "runtime-staging")
| summarize arg_max(Finished, Properties, Type, Branch, Source, Started, QueueName) by JobId
| project-rename JobType = Type) on JobId
| extend PropertiesJson = parse_json(Properties)
| extend OS = replace_regex(tostring(PropertiesJson.operatingSystem), @'\((.*)\).*|([^\(].*)', @'\1\2')
| extend Runtime = iif(PropertiesJson.runtimeFlavor == "mono", "Mono", iif(PropertiesJson.DefinitionName contains "coreclr", "CoreCLR", ""))
| extend TargetBranch = extractjson("$.['System.PullRequest.TargetBranch']", Properties)
| extend Architecture = PropertiesJson.architecture
| extend Scenario = iif(isempty(PropertiesJson.scenario), "--", PropertiesJson.scenario)
| project-away PropertiesJson
| order by Finished desc
};
crashes('System.Net.WebSockets.Client', true);
|
#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. |
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. |
I'm looking into it... |
Seen in https://dev.azure.com/dnceng/public/_build/results?buildId=1941374&view=results, but that stack is the same as #69125 |
Yes, we expect those 2 are dupes -- it was pending verification from @wfurt |
There is no failure in |
8/9:
Failures are on Linux only, with mix of architectures - arm64, amd64. Regression started on 8/5.
2 notable failures are on Rolling runs:
The text was updated successfully, but these errors were encountered: