Vlad Brezae

This bug can be easily reproduced in a matter of seconds with the following test case: ``` using System; using System.Threading; public struct VTWithRefs { public object o0, o1, o2,...

I can reproduce increasing high memory usage with this, which comes from managed memory, on random amd64 platform. I'm not sure if this is problem from testcase or bcl or...

@ayushm007 I'm not aware of great tools to use on linux. Normally I would recommend doing snapshots with Xamarin.Profiler (macos) and see what kind of objects are contributing to the...

This is actually not really a bug or a leak, but rather an extreme case of conservative stack scanning leading to memory waste due to the way the concurrent queue...

I remember seeing locks around enumeration/snapshot. Maybe we could safely break it off there ? Even if it doesn't guarantee us anything if the queue will not be enumerated on,...

There is no available fix yet and not sure when it will come, on mono. As suggested above, your other alternative would be to migrate your project over to .net...

@gkarabin Sounds plausible. `BlockingCollection` uses by default a `ConcurrentQueue` as a container internally

I'm not seeing anything weird on the runtime side, the application is just killed during its normal operation. There is a lot of contention on loader lock due to reflection...

@TomSoPolaris From what I can tell from the traces, the Newtonsoft serialization seems to be the main contributor to loader lock contention within your code. However, it seems to me...

During normal runtime shutdown all background threads are being aborted. I suspect this is the culprit