You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While other F6 games create state files which are smaller than 2KB, CG state files were 6.4 MB(!) (see #858).
BUT, while trying to narrow down the bug, the problem suddenly disappeared. Even after undoing all changes and even in 6.5.3! It turned out that deleting the old 6.4MB state files fixed the problem.
So it seem like there is a problem in the Serializer when overwriting large files and the files are not cut to their current length.
Looks like line 259 in StateManager could be fixed to use Serializer out(buf.str(), Serializer::Mode::ReadWriteTrunc);
The text was updated successfully, but these errors were encountered:
Saving all states also creates way too large files (e.g. 2 KB game with 160 MB for 1000 save states, single state is 1.2K). The value returned in RewindManager::saveAllStates() by state.data.size() is way tool large (156 KB).
@sa666666 This seems to result from a general bug in the 'RewindManager' and also causes excessive memory usage.
While other F6 games create state files which are smaller than 2KB, CG state files were 6.4 MB(!) (see #858).
BUT, while trying to narrow down the bug, the problem suddenly disappeared. Even after undoing all changes and even in 6.5.3! It turned out that deleting the old 6.4MB state files fixed the problem.
So it seem like there is a problem in the
Serializer
when overwriting large files and the files are not cut to their current length.Looks like line 259 in
StateManager
could be fixed to useSerializer out(buf.str(), Serializer::Mode::ReadWriteTrunc);
The text was updated successfully, but these errors were encountered: