Current PC setup is Win7 x64, Intel i7 2600k CPU, 12GB RAM, to describe general system specs.
I have been having a program crashing issue that started maybe 2-3 updates ago. It seems to be "restoring" itself through these program updates. I know that it began after months and months of zero problems.
The problem is very predictable in how it happens. IF S3D has just been opened to the first build table screen, the FFF process is clicked to edit, and a previously saved FFF is selected from the drop-down menus, it's an instant freeze->crash.
If S3D has just been opened and I click "prepare to print" first though, then back out to the primary screen, I can load another FFF from the drop-down without a crash.
If I attempt to save a new FFF after doing the last step mentioned (preview print, then back up a screen), I can typically save one time. If I apply more changes to the FFF, and try to update it right after a save that just worked it's almost always a freeze->crash. The conflict seems to revolve around the most recent FFF save stuck in memory. It's extremely hard to even create new FFFs anymore because of the crashes, it's almost like an ever-evolving profile is the best way to prevent the freeze and losing everything, which is a bit of a pain.
When S3D just updated recently, the program acted like it had reset itself as a default new program; it did carry over with it my printer's bed model which was reassuring that I didn't lose anything. To my surprise though, no previous FFF saves existed--uh oh. After running the program for seemingly just a few hours rebuilding some FFF configs I thought were gone, the next day I restarted the PC and the new program had reverted back exactly how it had been running before the update, and various preferences reverted back to how they were previously set before update also. At that point I thought for a moment I somehow lost the update, but when I checked for an available update, the software said it was up-to-date, at 3.1.0.
I gather there is something corrupt from wherever the program pulls stored user configs/preference info from after an update--though I'm not sure why the program ran like a new one until the next days restart and not upon the update install itself. During the few hours with a "clean-slate" program running I had after the update, I could not replicate the crash, so it has to be somehow tied to cached data.
When the program resumed my preferences and started crashing again, the FFFs I made in the meantime were gone. Where do the FFFs go if they can seemingly disappear before the program can pull them back? I wonder if this crashing problem is somehow tied to directory duplicates, or something similar than can happen when a new version is installed and the old version still remains on the computer.
Any help towards solving this would be much appreciated. Thanks!