Reduced memory usage and fixed several memory leaks (#933)

app/MindWork AI Studio/Components/MSGComponentBase.cs

@@ -5,7 +5,7 @@ using Microsoft.AspNetCore.Components;
 
 namespace AIStudio.Components;
 
-public abstract class MSGComponentBase : ComponentBase, IDisposable, IMessageBusReceiver, ILang
+public abstract class MSGComponentBase : ComponentBase, IDisposable, IAsyncDisposable, IMessageBusReceiver, ILang
 {
     [Inject]
     protected SettingsManager SettingsManager { get; init; } = null!;
@@ -103,10 +103,20 @@ public abstract class MSGComponentBase : ComponentBase, IDisposable, IMessageBus
         this.MessageBus.ApplyFilters(this, filterComponents, eventsList.ToHashSet());
     }
     
+    /// <summary>
+    /// Releases what this component has acquired. Override this instead of implementing
+    /// IDisposable again, so the deregistration from the message bus cannot be lost.
+    /// </summary>
     protected virtual void DisposeResources()
     {
     }
-    
+
+    /// <summary>
+    /// Releases what this component has acquired and needs an await to release. Override this
+    /// instead of implementing IAsyncDisposable, see the remarks on DisposeAsync below.
+    /// </summary>
+    protected virtual ValueTask DisposeResourcesAsync() => ValueTask.CompletedTask;
+
     #region Implementation of IDisposable
 
     public void Dispose()
@@ -116,4 +126,25 @@ public abstract class MSGComponentBase : ComponentBase, IDisposable, IMessageBus
     }
 
     #endregion
+
+    #region Implementation of IAsyncDisposable
+
+    /// <summary>
+    /// Releases this component asynchronously.
+    /// </summary>
+    /// <remarks>
+    /// This base class implements both ways of disposing on purpose. Blazor calls only DisposeAsync
+    /// when a component offers both, so a derived component which implements IAsyncDisposable on
+    /// its own would silently skip everything Dispose does — above all the deregistration from the
+    /// message bus, which holds a strong reference to every receiver. Deriving components override
+    /// DisposeResources or DisposeResourcesAsync instead, and this stays the one place which knows
+    /// about both.
+    /// </remarks>
+    public async ValueTask DisposeAsync()
+    {
+        await this.DisposeResourcesAsync();
+        this.Dispose();
+    }
+
+    #endregion
 }