Igor Bagdamyan

Is there any way to get a trace from F# compiler, at least a stack trace or smth?

@jkotas sorry to tag but maybe you can help here? What is the best way to diagnoze oom when app fails right away? I'm not sure how to collect traces...

This is an output of "free" util ``` total used free shared buff/cache available Mem: 4013232 828400 620368 215744 2564464 2237376 Swap: 0 0 0 ```

I've been able to collect a better trace by modifying fsc. Will try to look into it. Just in case I'm sharing it here [dotnet_20220818_213246.zip](https://github.com/dotnet/fsharp/files/9374246/dotnet_20220818_213246.zip)

@shushanhf I'm not sure. It is running in fact. I'd rather see it as GC/Jit bug to be honest. But this needs more investigation

Maybe there is some knobs on GC that need to be tuned or something is calculated incorretly in LA64. Max GC Heap Size: 34,337 MB It's doing lots of Start/Stop...

Tried a small app just to test allocations. App runs fine with 2gb heap and 1.2gb of gen0 and alloc rate of 150-180 megs/sec. Also, building F# app on windows...

Some new information: OOM is deterministic, it basically has this stack: ``` ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.String.Concat(String str0, String str1, String str2) at FSharp.Compiler.TcGlobals.initializer@1-4(TcGlobals this,...

@shushanhf You're welcome. If you need help please tell. I will do whatever I can :)

In your example CI is not abstract, it's a legit static member of that interface. You have to make this thing static virtual to get it working from T.