Repository navigation
Assert failure: m_alignpad == 0 in LibraryImportGenerator.Unit.Tests #68511
Description
pipeline: runtime-coreclr libraries-jitstress
job: net7.0-Linux-Release-arm64-CoreCLR_checked-zapdisable-(Ubuntu.1804.Arm64.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm64v8-20210531091519-97d8652
test: LibraryImportGenerator.Unit.Tests
+ grep COMPlus
COMPlus_ReadyToRun=0
COMPlus_TieredCompilation=0
COMPlus_DbgMiniDumpName=/home/helixbot/dotnetbuild/dumps/coredump.%d.dmp
COMPlus_ZapDisable=1
COMPlus_DbgEnableMiniDump=1
+ ./RunTests.sh --runtime-path /root/helix/work/correlation
----- start Mon Apr 25 08:18:44 UTC 2022 =============== To repro directly: =====================================================
pushd .
/root/helix/work/correlation/dotnet exec --runtimeconfig LibraryImportGenerator.Unit.Tests.runtimeconfig.json --depsfile LibraryImportGenerator.Unit.Tests.deps.json xunit.console.dll LibraryImportGenerator.Unit.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
popd
===========================================================================================================
/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.
Assert failure(PID 27 [0x0000001b], Thread: 41 [0x0029]): m_alignpad == 0
File: /__w/1/s/src/coreclr/vm/syncblk.cpp Line: 2952
Image: /root/helix/work/correlation/dotnet
Activity
jkotas commentedon Apr 25, 2022
Potentially same bug as #68443
[-]Assert failure: m_alignpad == 0[/-][+]Assert failure: m_alignpad == 0 in LibraryImportGenerator.Unit.Tests[/+]janvorli commentedon Apr 25, 2022
I've seen this issue in the past and at that time, it was related to mismatching managed and native view of class / struct sizes or mismatching view of those sizes by JIT / crossgen. That lead to writes behind the end of objects, corrupting the m_alignPad of the next object. But obviously this can be a completely different thing.
jkotas commentedon Apr 25, 2022
ReadyToRun is disabled for the run where the test is failing, so mismatch between JIT/crossgen layout algorithms cannot be the problem for this one.
janvorli commentedon Jul 12, 2022
Based on Kusto, this has been happening in the
readytorun\coreroot_determinism\coreroot_determinism\coreroot_determinismtest once or twice a week during the last 30 days or so.jkotas commentedon Jul 13, 2022
Duplicate of #70231