Crash 2016.8 when saving

[danj]

Got crash report when saving--it was taking a really long time to save (31 seconds versus normally about 4 or 5 seconds), and during the save process xlights crashed.   Debug report attached.

I had added some snowflake effects to the very end of the sequence just prior to saving

[Gilrock]

You sequence file didn't make it into the zip file.  Do you have any Data Layers in the sequence?

[Gilrock]

By the way this is similar to another crash you reported a week or so ago.  You are somehow causing a crash during a RenderAll in both cases.  Is there  something you are trying to do really quick like hit RenderAll and then drop an effect real quick or something like that?  We need to figure out what your workflow is that's causing this because it doesn't happen to me but developers tend to know what not to do.

[danj]

Thanks for looking, Gil.   No data layers in this sequence, just xlights effects.   I was not doing anything "fast" in this case.  In this case I hit the save button and was watching the save process down at the bottom left.  The crash only happened once; the rest of my saves/render-alls (after adding this effect to the WHM) worked fine with no problems.    The save time did go from around 4-5 seconds to about 28 seconds after dropping that effect onto the WHM.   I guess there was that much more info to render on all the models compared to before I dropped that effect onto the WHM?

[Gilrock]

Well that's what's strange is that the function it's dying in is RenderIseqData() which is the function that handles merging in data layers of which you don't have any.  But the function does erase data from the sequence data object but again not sure why that would be a problem.  But there has to be some operation we need to lock out from each other that we need to find.