CSC : error CS0041: Unexpected error writing debug information -- 'Insufficient memory to continue the execution of the program.'

[TonyValenti]

CSC : error CS0041: Unexpected error writing debug information -- 'Insufficient memory to continue the execution of the program.'

[jaredpar]

This is very likely not a real OOM scenario but likely a fragmentation issue or just bug in the DIA writing layer that the compiler is exposing. To debug though going to need to know more about what compilation is happening under the hood here.

@roji is there a way to get a binary log for the build that is happening here or surface the compilation in some way?

[roji]

/cc @AndriySvyryd, any idea how to get a binlog for dotnet ef dbcontext optimize (or some other way to diagnose this)?

[AndriySvyryd]

@roji @jaredpar OOM happens when compiling the generated code, so logs from dotnet ef dbcontext optimize wouldn't be very useful.

@TonyValenti Perhaps you can share the code generated by dotnet ef dbcontext optimize?

The current theory is that this is caused by the large number of unqualified lambdas (many of which are transformed into expression trees) in a single method.
See dotnet/efcore#33483

[TonyValenti]

Here you go.
Context.Generated.zip

[jaredpar]

@TonyValenti can you provide a compiler log of the build?

https://github.com/jaredpar/complog?tab=readme-ov-file#creating-compiler-logs

The generated code itself isn't going to be enough to track this down. Need to see it in the context of the greater build.

Note: that log will include basically all code in your project. So if it's not okay to share publicly please create a VS feedback ticket, share it there and put the link in this issue so I can assign it to my team.

[TonyValenti]

Here you go!
build.zip

[TonyValenti]

@jaredpar - Do you have everything you need?

[jaredpar]

@TonyValenti thanks for checking. I can repro this on my machine now with the provided compiler log.

[jaredpar]

@TonyValenti seems like my suspicion of this being an issue in DIA may be correct. Switching the compilation to use portable PDBs vs. Native PDBs causes the error to go away.

Short term you can flip to using <DebugType>Portable</DebugType> and that will get around the errorr

Note: is there a particular reason you're not already using portable PDBs? For .NET Core projects they're generally preferred.

[TonyValenti]

Hi @jaredpar -
I'm not explicitly setting DebugType type at all. But we do use PostSharp and it might set that (not sure though).

[jaredpar]

@TonyValenti the projects all seemingly have this import pattern at the top

	<Import Project="..\..\UniversalMigrator.Shared\__Shared\Shared.props" />

That Shared.props file has <DebugType>full</DebugType>

Note: I'm not familiar with PostSharp so unsure if this is / isn't related to that.