XLights freezing every 4 minutes - autosave?

[tripplett]

I have a SuperStar LOR pixel tree sequence that I imported into XLights.  I then started to edit it and add in effects for all my other elements.  However for some reason every 4 minutes XLights is freezing for about 45 seconds.  It is a large sequence, takes about 86 seconds to save.  I haven't done any sequencing this year till last week so I don't know when this would have started.  I upgraded to the .51 version before I did any sequencing this year.

If I view the Windows Resource Monitor it shows XLights unresponsive during these freezing times.  It also shows the cpu jumping up to 20% or so and disk activity jumping up.  The laptop I'm using is very powerful Alienware quad core i7 2.7GHz with 32g ram and dual solid state drives running raid 0.  Windows 10 64 bit.

Is there some type of auto save going on in the background or something?   I was running the production 2016.51 version but today I upgraded to 2016.54 Beta to see if it would help - it didn't.  This is really frustrating to use.  Just when I get going on some effect it locks up for 45 seconds.  I've tried to give good information here but if there is something I can add that will help please let me know.  I really want to polish up some of last years sequences this week as well as add another new one.

[markrvp]

Yes, go to:

SETTINGS->AUTO SAVE->(select 30 minutes)

It's probably set to the default of 3 minutes

[JonB256]

I never even notice my Auto saves. It only saves the XML data and that is a tiny amount compared to a full Render and Save of the FSEQ file. The 3 min autosave has been useful at least twice.

[pixelpuppy]

It only saves the XML data and that is a tiny amount compared to a full Render and Save of the FSEQ file.

Is that still true if he has the "render on save" option enabled?

[JonB256]

I have Render on Save checked.

[Gilrock]

Backups will never do a render.

[keithsw1111]

Auto save works fine if your sequence file is small. Once it gets big problems start to occur. If you do a import from another sequencer you can end up with a large sequence.