From cf15eb89506cf7fd6d5f107010f843cbc9357852 Mon Sep 17 00:00:00 2001 From: adelikat Date: Wed, 17 May 2017 13:20:57 -0500 Subject: [PATCH] TasStateManager - deciding upon a "fix" to the probable bug. This is technically different behavior than before but the intended behavior? This might break stuff --- BizHawk.Client.Common/movie/tasproj/TasStateManager.cs | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/BizHawk.Client.Common/movie/tasproj/TasStateManager.cs b/BizHawk.Client.Common/movie/tasproj/TasStateManager.cs index d22218a09c..3ad6d8ba90 100644 --- a/BizHawk.Client.Common/movie/tasproj/TasStateManager.cs +++ b/BizHawk.Client.Common/movie/tasproj/TasStateManager.cs @@ -427,10 +427,11 @@ namespace BizHawk.Client.Common state = BranchStates[frame][branch]; if (BranchStates[frame][branch].IsOnDisk) + { BranchStates[frame][branch].Dispose(); - else - ////Used -= (ulong)BranchStates[frame][branch].Length; - BranchStates[frame].RemoveAt(BranchStates[frame].IndexOfKey(branch)); // - feos, this runs only on hte else condition, I'm pretty sure this isn't intended? Check changeset a7b3668506ba62c40fd455bf36d919b4c5d92bf8 + } + + BranchStates[frame].RemoveAt(BranchStates[frame].IndexOfKey(branch)); if (BranchStates[frame].Count == 0) {