-
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
Assertion failed in test Interop\\ICustomMarshaler\\ConflictingNames\\MultipleALCs\\MultipleALCs.cmd: refCollectionObject != NULL #47696
Comments
Failed again in runtime-coreclr gcstress-extra 20210220.1 Failed test:
Error message:
|
I've been able to reproduce this locally - ran test for almost 3 hours and it finally triggered. I have a full DMP from a local build - source is the same minus some build code and an assert in unrelated section of code. Below are some details: Thread being inspected
GC thread. Frame 4 below is the issue. The loader allocator has a runtime/src/coreclr/vm/gcenv.ee.common.cpp Line 184 in fdc3f68
What is more disturbing are the results of the
The handle value from above is
|
/cc @janvorli |
fyi, saw this today on Windows arm64 gcstress0x3: |
Failed again in runtime-coreclr gcstress0x3-gcstress0xc 20210606.1 Failed test:
Error message:
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsRun: runtime-coreclr gcstress0x3-gcstress0xc 20210131.1 Failed tests:
Error message:
|
Moving to AssemblyLoader as this is related to unloadable ALCs. (Maybe should be VM-coreclr)? |
Failed again on windows-arm64 yesterday (see console.log)
@mangod9 Do you think someone on your team can take a look at the issue? |
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20210823.1 Failed test:
Error message:
|
assume this fails only with gcstress? |
Correct |
Disabled the test under GCStress in #58124 |
It looks like this issue is gone. I have reenabled the test and ran it overnight with GCStress 3 and tiered compilation off and all the runs passed. I am going to create a PR reenabling that test. |
I was unable to repro the issue dotnet#47696 anymore even after running the tests for more than a day in a loop, so I am reenabling GC stress for it. Close dotnet#47696
Run: runtime-coreclr gcstress0x3-gcstress0xc 20210131.1
Failed tests:
Error message:
The text was updated successfully, but these errors were encountered: