Dispose ClientChangesImpl ChangeSets to minimize memory footprint

[simantics/platform.git] / bundles / org.simantics.db.procore / src / fi / vtt / simantics / procore / internal / State.java

diff --git a/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java b/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
index 70e2cb10dd603122da7737bab85a2ea88bdc631a..3199901e90e191962c5815b6bde1623e39cda4f8 100644 (file)
--- a/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
+++ b/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
@@ -17,6 +17,7 @@ import java.util.concurrent.locks.Lock;
 import java.util.concurrent.locks.ReentrantLock;
 
 import org.simantics.db.ChangeSet;
+import org.simantics.db.Disposable;
 import org.simantics.db.Operation;
 import org.simantics.db.VirtualGraph;
 import org.simantics.db.common.utils.Logger;
@@ -331,6 +332,7 @@ class State {
                 // deny can always remove a persistent statement. 
                 clusterStream.reallyFlush();
 
+                Disposable.safeDispose(session.clientChanges);
                 session.clientChanges = new ClientChangesImpl(session);