Linux-x64 Runtime CLR Corruption

[stonstad]

Description

After upgrading from .NET 9.0 to 10.0, I have seen a consistent stream of runtime errors which appear to indicate type and runtime corruption in the CLR. Here is one example of an exception I am seeing.

Exception Message: "No parameterless constructor defined for type 'y.talMovingInHorizontalPlane'."
Exception Stack Trace: "Error Resolving StackTrace: Format of the executable (.exe) or library (.dll) is invalid."

'y.talMovingInHorizontalPlane'' isn't a valid type in my code and it likely refers to a public bool field named "IsOrbitalMovingInHorizontalPlane". The truncation and/or name corruption is suggestive of memory corruption.

This behavior does not manifest on windows-64. It does consistently manifest on linux-x64, via an Azure App Service configured for Linux and .NET 10.0.

Reproduction Steps

Unknown at this time.

Expected behavior

The runtime should not throw random exceptions with corrupt type names when running on Linux-64.

Actual behavior

The runtime throws random exceptions with corrupt type names. The associated stack trace is "Error Resolving StackTrace: Format of the executable (.exe) or library (.dll) is invalid.". The errors are seemingly random and involve non-sensical concepts, such as a bool field missing a parameterless constructor.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[mangod9]

Would you be able to share a dump of the failure?

[janvorli]

@stonstad does your app have any unsafe code or does it pinvoke into some native shared library that's not part of .NET?

[agocke]

If not a dump, a stack trace would be great.

[stonstad]

Would you be able to share a dump of the failure?

I would be happy to. The bugged behavior does not terminate the process to produce a dump file and it is running remotely in an Azure App Service. Would I still be able to generate a dump?

[stonstad]

If not a dump, a stack trace would be great.

The exception is logged and reports the stack trace as "Error Resolving StackTrace: Format of the executable (.exe) or library (.dll) is invalid." It does not show any associated call stack at all.

It is worth noting that the executable continues to run and this isn't a platform vs DLL compilation issue. Execution continues, but these random exceptions are thrown.

[stonstad]

@stonstad does your app have any unsafe code or does it pinvoke into some native shared library that's not part of .NET?

No unsafe code.

[stonstad]

Pinging @jkotas, @agocke , and @janvorli. Questions above are answered. Hope it is OK to ping you. Just didn't want this update to be missed. Thank you again.

[jkotas]

We need a crash dump to investigate. Are you able to get one?

Error Resolving StackTrace

This error message does not exist in dotnet/runtime. Do you know happen to know what's producing it? I do not think that it is .NET runtime itself, it must be some component external to the runtime.