Add [HandleProcessCorruptedStateExceptions] attribute to the event loop

- needed so that we can catch AccessViolationExceptions and terminate the process

Author: KrzysFR

FoundationDB.Client/Fdb.cs

@@ -36,6 +36,7 @@ namespace FoundationDB.Client
 	using System;
 	using System.Diagnostics;
 	using System.Runtime.CompilerServices;
+	using System.Runtime.ExceptionServices;
 	using System.Threading;
 	using System.Threading.Tasks;
 	using SystemIO = System.IO;
@@ -307,6 +308,7 @@ private static void StopEventLoop()
 		}
 
 		/// <summary>Entry point for the Network Thread</summary>
+		[HandleProcessCorruptedStateExceptions]
 		private static void EventLoop()
 		{
 			//TODO: we need to move the crash handling logic outside this method, so that an app can hook up an event and device what to do: crash or keep running (dangerous!).

FoundationDB.Client/FdbFutureSingle.cs

@@ -252,14 +252,14 @@ protected override void CloseHandles()
 		protected override void CancelHandles()
 		{
 			var handle = m_handle;
-			//REVIEW: there is a possibility of a race condition with Dispoe() that could potentially call FutureDestroy(handle) at the same time (not verified)
+			//REVIEW: there is a possibility of a race condition with Dispose() that could potentially call FutureDestroy(handle) at the same time (not verified)
 			if (handle != null && !handle.IsClosed && !handle.IsInvalid) FdbNative.FutureCancel(handle);
 		}
 
 		protected override void ReleaseMemory()
 		{
 			var handle = m_handle;
-			//REVIEW: there is a possibility of a race condition with Dispoe() that could potentially call FutureDestroy(handle) at the same time (not verified)
+			//REVIEW: there is a possibility of a race condition with Dispose() that could potentially call FutureDestroy(handle) at the same time (not verified)
 			if (handle != null && !handle.IsClosed && !handle.IsInvalid) FdbNative.FutureReleaseMemory(handle);
 		}