Some collection modified safety in Dispatch (seeing a few exceptions on Rust staging)

Facepunch.Steamworks/Classes/Dispatch.cs

@@ -65,12 +65,23 @@ namespace Steamworks
 			SteamAPI_ManualDispatch_Init();
 		}
 
+		/// <summary>
+		/// Make sure we don't call Frame in a callback - because that'll cause some issues for everyone.
+		/// </summary>
+		static bool runningFrame = false;
 
 		/// <summary>
 		/// Calls RunFrame and processes events from this Steam Pipe
 		/// </summary>
 		internal static void Frame( HSteamPipe pipe )
 		{
+			if ( runningFrame )
+				return;
+
+			try
+			{
+				runningFrame = true;
+
 				SteamAPI_ManualDispatch_RunFrame( pipe );
 				SteamNetworkingUtils.OutputDebugMessages();
 
@@ -88,6 +99,19 @@ namespace Steamworks
 					}
 				}
 			}
+			finally
+			{
+				runningFrame = false;
+			}
+		}
+
+		/// <summary>
+		/// To be safe we don't call the continuation functions while iterating
+		/// the Callback list. This is maybe overly safe because the only way this
+		/// could be an issue is if the callback list is modified in the continuation
+		/// which would only happen if starting or shutting down in the callback.
+		/// </summary>
+		static List<Action<IntPtr>> actionsToCall = new List<Action<IntPtr>>();
 
 		/// <summary>
 		/// A callback is a general global message
@@ -108,13 +132,22 @@ namespace Steamworks
 
 			if ( Callbacks.TryGetValue( msg.Type, out var list ) )
 			{
+				actionsToCall.Clear();
+
 				foreach ( var item in list )
 				{
 					if ( item.server != isServer )
 						continue;
 
-					item.action( msg.Data );
+					actionsToCall.Add( item.action );
 				}
+
+				foreach ( var action in actionsToCall )
+				{
+					action( msg.Data );
+				}
+
+				actionsToCall.Clear();
 			}
 		}