Hi,

We have high throughput application that generates thousands of tasks per second doing some processing on aerospike records in parallel. Its all good when load is relatively small, but when we want to activate 250k records in parallel (we have Semaphore which limits each batch at 1000) we start experiencing deadlock scenarios. I've created a dump file and I observed that 85.27% (according to Visual Studio analyzer)  of the current tasks are all stuck with this call stack:

```
 	System.Private.CoreLib.dll!System.Reflection.Assembly.Load(System.Reflection.AssemblyName assemblyRef) Line 53	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.ObjectReader.ResolveSimpleAssemblyName(System.Reflection.AssemblyName assemblyName) Line 871	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.ObjectReader.FastBindToType(string assemblyName, string typeName) Line 830	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo assemblyInfo, string name) Line 924	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.ObjectMap.ObjectMap(string objectName, string[] memberNames, System.Runtime.Serialization.Formatters.Binary.BinaryTypeEnum[] binaryTypeEnumA, object[] typeInformationA, int[] memberAssemIds, System.Runtime.Serialization.Formatters.Binary.ObjectReader objectReader, int objectId, System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo assemblyInfo, System.Runtime.Serialization.Formatters.Binary.SizedArray assemIdToAssemblyTable) Line 64	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.BinaryParser.ReadObjectWithMapTyped(System.Runtime.Serialization.Formatters.Binary.BinaryObjectWithMapTyped record) Line 558	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.BinaryParser.Run() Line 117	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(System.Runtime.Serialization.Formatters.Binary.BinaryParser serParser) Line 129	C#
 	System.Runtime.Serialization.Formatters.dll!System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(System.IO.Stream serializationStream) Line 149	C#
>	AerospikeClient.dll!Aerospike.Client.ByteUtil.BytesToObject(byte[] buf, int offset, int len) Line 147	C#
 	AerospikeClient.dll!Aerospike.Client.Unpacker.UnpackBlob(int count) Line 191	C#
 	AerospikeClient.dll!Aerospike.Client.Unpacker.UnpackObject() Line 282	C#
 	AerospikeClient.dll!Aerospike.Client.Unpacker.UnpackList(int count) Line 64	C#
 	AerospikeClient.dll!Aerospike.Client.ByteUtil.BytesToParticle(int type, byte[] buf, int offset, int len) Line 58	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncRead.ParseRecord(int opCount, int fieldCount, int generation, int expiration) Line 158	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncRead.ParseResult() Line 86	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncSingleCommand.ParseCommand() Line 18	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncCommand.ReceiveEvent() Line 491	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncCommand.ReceiveEvent() Line 464	C#
 	AerospikeClient.dll!Aerospike.Client.AsyncCommand.EventHandlers.HandleSocketEvent(object sender, System.Net.Sockets.SocketAsyncEventArgs args) Line 40	C#
 	System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Line 183	C#
 	System.Net.Sockets.dll!System.Net.Sockets.SocketAsyncEngine.System.Threading.IThreadPoolWorkItem.Execute() Line 261	C#
 	System.Private.CoreLib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch() Line 729	C#
 	System.Private.CoreLib.dll!System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Line 63	C#

``` 

I know it sounds bizarre but I think because the load that we generate is not gradual but rather 1k at once, it might relate to Assembly.Load deadlocking