-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests segfault in Mono #81249
Comments
There's another issue representing a crash in source generators on mono that's been plaguing us in CI: |
@danmoseley this is mono, so it would be better to point some mono folks to this. The coreclr runtime team doesn't have experience debugging mono. |
@janvorli - doh - of course, brainstorm. Thanks. @SamMonoRT there's a dump here if you want it, not sure how long before they time out. |
@lambdageek - can you take an initial look |
Thread 10 looks ok, actually. it's just doing some work. Thread 9 looks like it crashed:
and some output from
Frames 7 and 8 look like JITed code. we'll need to try repro locally.
|
@lambdageek the links to builds in #81123 might contain coredumps. |
@lambdageek as another data point the crashes only seem to happen on arm64 |
Got it to crash in a VM after a couple of hours of running the test in a loop. Not the same crash as this issue, unfortunately. An assertion failure during class setup due to - I'm guessing - a data race: g_assert (klass == klass->supertypes [klass->idepth - 1]); I see two threads in I can't convince myself that it would cause the same kinds of failures we see in the CI jobs. |
Probably same as #81123 - which is a very similar stack trace in the Roslyn3.11 test suite. Going to try running that other testsuite in a loop, too |
Seen again in an unrelated PR in
Callstacks (expand)
|
This is a dupe of #81123 |
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-81202-merge-135c923415104d6c85/Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests/1/console.6c3784b3.log?helixlogtype=result
net8.0-linux-Debug-arm64-Mono_release-(Ubuntu.1804.Arm64.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm64v8
Possible stack trace for the crash
(original issue description note: this is not the problematic stack trace)
Not sure how it indicates which thread failed, but I'm guessing it's this one?
there is a core dump
https://dev.azure.com/dnceng-public/public/_build/results?buildId=148909&view=ms.vss-test-web.build-test-results-tab&runId=3170018&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=200309
The text was updated successfully, but these errors were encountered: