Skip to content
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

Assert failure: LoaderHeap must return zero-initialized memory #111140

Closed
WangyangZhou90 opened this issue Jan 7, 2025 · 2 comments
Closed

Assert failure: LoaderHeap must return zero-initialized memory #111140

WangyangZhou90 opened this issue Jan 7, 2025 · 2 comments
Assignees
Labels
area-VM-coreclr needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Comments

@WangyangZhou90
Copy link
Contributor

WangyangZhou90 commented Jan 7, 2025

Failed in: Pipelines - Run 20250106.1
Error message:

C:\h\w\A52C0925\w\BF600A68\e>call baseservices\exceptions\baseservices-exceptions\baseservices-exceptions.cmd -usewatcher 
BEGIN EXECUTION
"C:\h\w\A52C0925\p\watchdog.exe" 29 "C:\h\w\A52C0925\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  baseservices-exceptions.dll 

Assert failure(PID 3916 [0x00000f4c], Thread: 1932 [0x078c]): LoaderHeap must return zero-initialized memory

CORECLR! UnlockedLoaderHeap::UnlockedAllocMem_NoThrow + 0x3B2 (0x00007fff`7670dbe2)
CORECLR! UnlockedLoaderHeap::UnlockedAllocMem + 0x103 (0x00007fff`7670c8f3)
CORECLR! LoaderHeap::RealAllocMemUnsafe + 0x68 (0x00007fff`75f97878)
CORECLR! MethodTableBuilder::AllocateNewMT + 0x7D9 (0x00007fff`763ceb19)
CORECLR! MethodTableBuilder::SetupMethodTable2 + 0x1046 (0x00007fff`763fb836)
CORECLR! MethodTableBuilder::BuildMethodTableThrowing + 0x176A (0x00007fff`763d234a)
CORECLR! ClassLoader::CreateTypeHandleForTypeDefThrowing + 0x1897 (0x00007fff`763d8f47)
CORECLR! ClassLoader::CreateTypeHandleForTypeKey + 0x6E5 (0x00007fff`76037e75)
CORECLR! ClassLoader::DoIncrementalLoad + 0x631 (0x00007fff`76039c71)
CORECLR! ClassLoader::LoadTypeHandleForTypeKey_Body + 0x1064 (0x00007fff`76046ee4)
    File: D:\a\_work\1\s\src\coreclr\utilcode\loaderheap.cpp:1457
    Image: C:\h\w\A52C0925\p\corerun.exe

App Exit Code: -1073740286
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
[XUnitLogChecker]: 04:11:13.10: The full run will be done.
[XUnitLogChecker]: 04:11:13.11: No logs were found. This work item was skipped.
[XUnitLogChecker]: 04:11:13.11: If this is a mistake, then something went very wrong. The expected temp log name would be: 'baseservices-exceptions.tempLog.xml'
ERROR: The process "corerun.exe" not found.
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jan 7, 2025
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jan 7, 2025
@jkotas jkotas changed the title ERROR: The process "corerun.exe" not found. Assert failure: LoaderHeap must return zero-initialized memory Jan 7, 2025
Copy link
Contributor

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

@WangyangZhou90
Copy link
Contributor Author

closed, reopen as needed.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-VM-coreclr needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners
Projects
None yet
Development

No branches or pull requests

4 participants