@bian-womp/spark-remote 0.3.51 → 0.3.53

package/lib/cjs/index.cjs

@@ -327,7 +327,6 @@ class HttpPollingTransport {
     }
 }
 
-/* eslint-disable @typescript-eslint/no-explicit-any */
 function summarize(value, maxLen = 120) {
     try {
         const s = typeof value === "string" ? value : JSON.stringify(value);
@@ -447,6 +446,24 @@ async function createServerRuntimeAdapter(id, createRegistry, send, extensions)
             });
         },
         build: async (def, opts) => {
+            // If we rebuild the graph, we must not keep the previous runtime/engine alive.
+            // This can happen for a single "flow" when:
+            // - server bootstraps an empty graph (no snapshot) then client sends Build with real def
+            // - snapshot load / applySnapshotFull triggers a build
+            // - client intentionally rebuilds the graph
+            //
+            // Without disposing, we can end up with multiple GraphRuntime instances in memory
+            // for the same flow/connection, each holding listeners/resources.
+            if (engine) {
+                console.info(`[ServerRuntimeAdapter:${id}] Disposing previous engine before building new one`);
+                engine.dispose();
+                engine = undefined;
+            }
+            if (graphRuntime) {
+                console.info(`[ServerRuntimeAdapter:${id}] Disposing previous graph runtime before building new one`);
+                graphRuntime.dispose();
+                graphRuntime = undefined;
+            }
             const environment = opts?.environment || {};
             graphRuntime = builder.build(def, {
                 environment,