Why, oh, why is the new version "recovery saving" so often?

[Anonymous]

Besides "recovery saving" about every 5 minutes, it is apparently pummelling the CPU and memory (RAM).  I can manually save, and within seconds, the "recovery save" kicks in and my CPU and memory fans go into high-gear and "Fusion 360 is not responding..." Anyone else seeing this issue? I have not installed anything new.

I am on an Alienware gaming system with 32 gigs of ram, and 8 gigs of dedicated video RAM with the GPU (Geforce GTX 1080)... and I only have one model open. There is no reason it should take 15 to 20 seconds to "recovery save" a single model, which is strange because it also still periodically "auto-saves" too... seems a little redundant, I know there is a difference, I'm just saying it's a lot of saving and slowwwwww, OMG this recovery save is murdering me.  All the same models I always work with and only making minor iterative changes.   The timing syncs up with the latest version and boy is it painfully slow with the recovery save, so much so it behaves like it has a memory leak. After I am ready to put myself out of the misery of this, I have just enough energy left after saying "what the hell?" about 100 times to restart the system (only Fusion 360 is running) then it will go a faster for about an hour, or so but it slowly ...uh...slows down more and more.  And I am not even doing CAM at all.  I am afraid of what kind of slow death that will feel like.  It's so bad, I had to remind myself that the software isn't watching and waiting until I am extra tired of this then BOOM! there it is again.

Standard stuff, yes, fast internet, no I have not deleted all the projects from my hub's dashboard, everything was going swimmingly until the last update (2.0.5357), plenty of hard drive space, no I have not had too many beers again (yet). And, unfortunately, I cannot share the models unless you are in the military with active security clearance. They are pretty basic assemblies with with less than 25 parts in a single model (each). I guess I am trying to figure out if others are seeing this same thing.

Thanks, guys.

[HughesTooling]

This is something that definitely seems worse over the last 3 or 4 months and has had several threads about it. I don't know if they've made it more aggressive because there used to be a lot of complaints that autosave didn't work well for some people. Haven't noticed there being Recovery saves and Auto saves, is the auto save because you have Auto save on exit enabled? Don't think you mentioned you hard drive, is it an SSD?

You would think the save could be done in the background but perhaps they need to freeze everything to make the save safe.

Mark

[jeff_strater]

@Anonymous , you can control the frequency of the recovery save in the preferences dialog:

the recovery save is time-based.  If yours is set to 5 mins, it will auto-backup every 5 mins.

The duration of the save is completely dependent on the size of the model.  If it is large, it will definitely take a while.  And "large" doesn't just mean number of components.  If each of your 25 components has a lot of complex geometry, that will affect save.  Even your design style can bloat the model.  Certain solid features create caches of bodies, and if those bodies are large, they do take up space.

And, no, Fusion cannot do this save in another thread.  It cannot save a model that is in the process of being modified.

[HughesTooling]

@jeff_strater  I have a couple of questions. What happens if you have several files open, is the recovery save based on the time each file was opened? So if you open 4 designs 1 minute apart you'd get a recovery save every minute?

And if you have a design open but not modified is it still going to generate recovery save? And the same question for a file you have open, modify then save so is open in a saved state.

Mark

[jeff_strater]

Those are really good questions, @HughesTooling .  I need to check to make sure, but my understanding is this:

• the timer is session-based, not document based.  That is, there is one timer that goes off when the time has expired
• all open documents are then queried to see if they have been modified since the last save or auto-save 
• a backup version for any document that is in this dirty state then is created
• if a command is running, a backup version cannot be created.  This is kind of a weird Fusion-ism.  It's because Save itself is a command, and starting any command will terminate any active command.  This is what sometimes bites people.  If you spend all your time with an active command running, you never get a backup created.  If Fusion crashes, then there is no recent recovery file

However, I need to check the above to make sure it is accurate.

[ahsan.autodesk]

Hi @Anonymous,
Can you please share your Diagnostic log files with us? We would like to dig a bit deeper into this. This is certainly unexpected.
Sorry for the inconvenience.
Thx and regards,
Ahsan

[Anonymous · Accepted solution]

Sorry it took so long for my reply, I was too busy when we were having the problem to reply.  It seems to be improved since the last few updates.  We were seeing it on two different computers (and we run Alienware PCs).  Luckily, it seems resolved.  I'll go ahead and close this since we are not seeing it now.

Thank you very much.

-C