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
Segmentation fault in LibraryImportGenerator.Unit.Tests #68443
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:
/root/helix/work/workitem/e /root/helix/work/workitem/e
Discovering: LibraryImportGenerator.Unit.Tests (method display = ClassAndMethod, method display options = None)
Discovered: LibraryImportGenerator.Unit.Tests (found 121 of 126 test cases)
Starting: LibraryImportGenerator.Unit.Tests (parallel test collections = on, max threads = 4)
LibraryImportGenerator.UnitTests.Compiles.ValidateSnippetsWithMarshalType [SKIP]
No current scenarios to test.
./RunTests.sh: line 168: 24 Segmentation fault (core dumped) "$RUNTIME_PATH/dotnet" exec --runtimeconfig LibraryImportGenerator.Unit.Tests.runtimeconfig.json --depsfile LibraryImportGenerator.Unit.Tests.deps.json
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.
(lldb) frame select 5
frame #5: 0x0000007fae239df4 libcoreclr.so`WKS::gc_heap::mark_object_simple(po=<unavailable>) at gc.cpp:24041:17
(lldb) frame variable
(uint8_t **) po = <variable not available>
(const int) thread = 0
(uint8_t *) o = 0x0000001561a16fe8 "\xc1\"\xa1a\U00000015"
(int) condemned_gen = 0
(size_t) s = 127
(uint8_t *) class_obj = <variable not available>
(uint8_t **) poo = <no location, value may have been optimized out>
(lldb) dumpobj 0x0000001561a16fe8
<Note: this object has an invalid CLASS field>
Invalid object
changed the title [-]Segmentation fault in LibraryImportGenerator.Unit.Tests (linux-arm64)[/-][+]Segmentation fault in LibraryImportGenerator.Unit.Tests[/+]on Apr 25, 2022
With that removed I observe that the latest windows failure looks unrelated?
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.
Activity
danmoseley commentedon Apr 23, 2022
from the one above,
I can't get managed frames, if they matter, as below. Not sure why:
danmoseley commentedon Apr 23, 2022
BTW, to find future such dumps (currently this is the only recent one) run this query
Execute: Web | Desktop | Web (Lens) | Desktop (SAW)
https://engsrvprod.kusto.windows.net/engineeringdata
the URI column contains a link to the how-to-debug-dump.md for each, which has a link to the dump etc.
hez2010 commentedon Apr 23, 2022
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
danmoseley commentedon Apr 23, 2022
Seems this is #68112 ?
jkotas commentedon Apr 25, 2022
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).
jkotas commentedon Apr 25, 2022
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.
jkotas commentedon Apr 25, 2022
!verifyheapprints thousands of missing card_table entry messages, like:7 remaining items
[-]Segmentation fault in LibraryImportGenerator.Unit.Tests (linux-arm64)[/-][+]Segmentation fault in LibraryImportGenerator.Unit.Tests[/+]mangod9 commentedon Apr 25, 2022
From the query @danmoseley provided above appears that the failure is Linux only, are there any windows dumps available per Jan's comment above?
danmoseley commentedon Apr 25, 2022
Remove this from query
| where ExitCode ==139
mangod9 commentedon Apr 25, 2022
jkotas commentedon Apr 25, 2022
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.
jkotas commentedon Apr 25, 2022
A good Windows dump to look at is: https://dev.azure.com/dnceng/public/_build/results?buildId=1701571&view=ms.vss-test-web.build-test-results-tab&runId=46386632&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=200605 (it is from #67184).
mangod9 commentedon Apr 25, 2022
Thanks, we will take a look. @PeterSolMS
jkotas commentedon May 10, 2022
Fixed by #69106
Add the repro case for github issue dotnet#68443 (dotnet#68443) as a …
Add the repro case for github issue #68443 (#68443) as a GC test case. (