Running ww.fix causes RAM spike, rendering game inoperable

[VNex]

Title says most of it.

 

Extra details:  When running ww.fix my RAM usage will spike from around 5GB, typical for game-play, to 23.99 GB (the max I have available); with a RAM cleaner I can get it down to about 21 / 22 GB.  It will run, and it will finish, but the RAM spike won't go down until I use Task Manager to force the game to close.  Which, not to point out the obvious, makes the ww.fix I just spent 20 minutes (or more) on moot.

 

I did notice that the .fix notices were new, so is this RAM spike just needing to be streamlined?  Do I have something extra in my files, or something missing, causing it?  Other options?  Is it yet another problem caused by Neighborhood Stories?

[TURBODRIVER]

Hey. Sounds like you must have a massive game and fixing loads every single Sim in the game and all of their data to process it all which produces even more data. I haven't seen anything like this happen before, but I can add some memory cleaning solutions along the way, it will make the process longer but shouldn't overload the system.

[SkyBarbie]

I noticed that Turbodriver revamped the 'ww.fix' functionality for version 169a.  It really taxes my system also and I have a high performance gaming rig.  A couple of times I thought it locked up my computer as nothing responded for a minute but The Sims 4 started working again eventually.  That is happening with an M.2 NVME ultra fast SSD and 32 GB of high speed RAM.  I'm sure some players think it locks up their computer on slower systems as it would take even longer to finish and for the game to start responding again.  I do have 275 Sims in my world.