Sean Meighan

Software => Bugs in xLights/Nutcracker => Topic started by: brett on June 27, 2018, 02:35:04 AM

Title: bulk edit crash on 2018.18
Post by: brett on June 27, 2018, 02:35:04 AM: Ran into a number of issues tonight with bulk edit crashing in a number of spots. Was able to reliably reproduce the crash and get a dump when trying to bulk edit a number of render styles on a number of effects. reproduced the crash with only 2 effects as well as with as many as 50+.

Files attached. I'm good for now, as 2018.16 seems OK, but wanted to let you guys know if there is something to look at. Let me know if you need me to try to reproduce again.

-Brett
Title: Re: bulk edit crash on 2018.18
Post by: keithsw1111 on June 27, 2018, 03:47:13 AM: This only occurs when bulk editing outside the effect panel and will be fixed in the next release.
Title: Re: bulk edit crash on 2018.18
Post by: brett on June 29, 2018, 09:58:23 PM: Hey Keith. Just launced .19, first three bulk edit from effect pane crashed (different effects, different # of effects), uploads attached. just wanted to let you know, let me know if you think I have a setup issue.
Title: Re: bulk edit crash on 2018.18
Post by: keithsw1111 on June 30, 2018, 03:29:45 AM: Which effects. Which properties

Sent from my iPhone using Tapatalk
Title: Re: bulk edit crash on 2018.18
Post by: brett on June 30, 2018, 04:50:31 AM: Hi Keith

The first one that I uploaded specifically were X/Y positionchanges on Shockwave in the effect panel.

The second one was a (if i remember correcly) a change to "Start Intensity" on the "On" effect.

Running windows 10 version. I can try to re-install and run a couple more scenarios if that is helpful.

Thanks,
Brett
Title: Re: bulk edit crash on 2018.18
Post by: keithsw1111 on June 30, 2018, 06:54:40 AM: I have tried both in .19 and neither crash
Title: Re: bulk edit crash on 2018.18
Post by: Gilrock on June 30, 2018, 08:03:12 AM: Full re-install of Windows 10 usually fixes it. :)
Title: Re: bulk edit crash on 2018.18
Post by: keithsw1111 on July 01, 2018, 05:13:38 AM: Ok Brett ... found it ... Lithgow reproduced it and showed me. It will be fixed in .20 ... still not sure how this bug ever worked.