-
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
Segmentation fault in LibraryImportGenerator.Unit.Tests #68443
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. |
Tagging subscribers to this area: @dotnet/interop-contrib Issue DetailsUse this issue to track Segmentation fault on linux-arm64 only. Open separate issue for other types of failures in LibraryImportGenerator.Unit.Tests test. Log:
Details (failed in #68436): https://dev.azure.com/dnceng/public/_build/results?buildId=1734505&view=ms.vss-test-web.build-test-results-tab&runId=46962718&resultId=188668&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab Earlier issue tracking the same failure #67031
|
from the one above,
I can't get managed frames, if they matter, as below. Not sure why:
|
BTW, to find future such dumps (currently this is the only recent one) run this query https://engsrvprod.kusto.windows.net/engineeringdata let wi =
WorkItems
| join kind=leftsemi (Jobs | where Queued > ago (3d) ) on $left.JobName == $right.Name
| where ExitCode != 0
| where FriendlyName == "LibraryImportGenerator.Unit.Tests";
Files
| lookup kind=inner wi on $left.WorkItemName == $right.Name
| where ExitCode ==139
| where FileName == "how-to-debug-dump.md"
| join WorkItems on $left.WorkItemName == $right.Name
| join Jobs on $left.JobName == $right.Name
| extend PhaseName = tostring(parse_json(Properties)["System.PhaseName"]),
Pipeline = tostring(parse_json(Properties).DefinitionName),
BuildId = tostring(parse_json(Properties).BuildId)
| where Pipeline !contains("jitstress")
| project Timestamp, QueueName, ExitCode, Uri, ConsoleUri, PhaseName, Pipeline, BuildId the URI column contains a link to the how-to-debug-dump.md for each, which has a link to the dump etc. |
I pushed a new commit to the PR before CI completion, so the test details were lost. But I recorded the helix log url of this failure in advance: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-68436-merge-e86832cd40d54e21a1/LibraryImportGenerator.Unit.Tests/1/console.58e9f1eb.log?sv=2019-07-07&se=2022-05-13T16%3A12%3A02Z&sr=c&sp=rl&sig=YTfbYaCN9shqYcxAyoFzSiWV1ChCBco2Z3uBhvkUa%2Fo%3D |
Seems this is #68112 ? |
This is arm64 dump and you are setup for x64 (the log you have shared says "Target OS: LINUX Architecture: X64"). This is the managed part of the stack for reference (as you have said, it probably does not matter).
|
I do not think it is #68112. The problem is that the object that we are marking in frame 5 is invalid. We happen to take the path for collectible types based on the invalid data.
|
|
Tagging subscribers to this area: @dotnet/gc Issue DetailsUse this issue to track Segmentation fault on linux-arm64 only. Open separate issue for other types of failures in LibraryImportGenerator.Unit.Tests test. Log:
Details (failed in #68436): https://dev.azure.com/dnceng/public/_build/results?buildId=1734505&view=ms.vss-test-web.build-test-results-tab&runId=46962718&resultId=188668&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab Earlier issue tracking the same failure #67031
|
The crash with the same signature is getting hit on both Windows and Linux, and both x64 and arm64. I am removing the linux-arm64 specific label. |
From the query @danmoseley provided above appears that the failure is Linux only, are there any windows dumps available per Jan's comment above? |
Remove this from query | where ExitCode ==139 |
This comment was marked as off-topic.
This comment was marked as off-topic.
Yes, this is unrelated problem from the runs triggered by unmerged PR that has a bug on startup path and so all tests are crashing on it. I only looked at the crashes from main or from PRs that got merged. I am not sure whether there is a good way to filter out the PR specific problems in the Kusto query. |
Thanks, we will take a look. @PeterSolMS |
Fixed by #69106 |
#69496) Let's figure out later whether this test should be part of the GC stress test and/or be added to a CI config.
Use this issue to track Segmentation fault with stacktrace similar to #68443 (comment) only. Open separate issue for other types of failures in LibraryImportGenerator.Unit.Tests test.
Log:
Details (failed in #68436): https://dev.azure.com/dnceng/public/_build/results?buildId=1734505&view=ms.vss-test-web.build-test-results-tab&runId=46962718&resultId=188668&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
Earlier issue tracking the same failure #67031
The text was updated successfully, but these errors were encountered: