Save Setup unresponsive

[ozaz]

I've noticed, since a few updates ago, that Save Setup make xLights unresponsive for a considerable period of time.  Have had this issue on (at least) .33 .34 and .35

The attached screen shot shows xLights not responding. I had time to deliberate, open snipping tool, take a screen shot, save it and start this thread before Save Setup had finished!
The only thing I'd changed was the number of channels of DMX.
It doesn't happen every time (of course) but most times.

Happens on both my PCs, the slow schedule PC and the superfast laptop, both run latest Win 10 - V1709.

from laptop, an i7-6700K @4.00GHz; 16GB RAM, 256GB SSD, nVidia GeForce GTX 980M video card - so specs are OK

task manager shows xLights using about 13% CPU (total CPU 15%) and about 420MB RAM - whilst "saving"
once completed xLights shows about .3% CPU and 360MB RAM

No errors or crash reports so not much else I can provide

Has anyone else noticed this issue? Is this an xLights issue, or possibly something related to latest Win 10? Or some combination?

All pertinent assistance greatly appreciated.

Cheers

OzAz

[keithsw1111]

Maybe send us your networks and rgbeffects files

[davidwill]

I have the same thing happened for some time now. I wasn't sure if it was my computer, and it seems like xlights crashes alot for me, which is prob me or my computer since we are both old. Lol. I haven't sent the crash reports since I can never remember where to send them. Thanks

Sent from my SAMSUNG-SM-G900A using Tapatalk

[keithsw1111]

I have the same thing happened for some time now. I wasn't sure if it was my computer, and it seems like xlights crashes alot for me, which is prob me or my computer since we are both old. Lol. I haven't sent the crash reports since I can never remember where to send them. Thanks

Sent from my SAMSUNG-SM-G900A using Tapatalk

In which case it is a bit of a lottery if it will get fixed or not. The fastest way to get t fixed is to reliably reproduce a problem and help the devs reproduce it.

[davidwill]

I have the same thing happened for some time now. I wasn't sure if it was my computer, and it seems like xlights crashes alot for me, which is prob me or my computer since we are both old. Lol. I haven't sent the crash reports since I can never remember where to send them. Thanks

Sent from my SAMSUNG-SM-G900A using Tapatalk

In which case it is a bit of a lottery if it will get fixed or not. The fastest way to get t fixed is to reliably reproduce a problem and help the devs reproduce it.

I know, so when I get home I will send the crash reports to? 

Sent from my SAMSUNG-SM-G900A using Tapatalk

[keithsw1111]

Post them here. Send them to me. Post them on GitHub.

[ozaz]

For Keith - network and rgb files attached

It's probably something dumb I've done, it usually is. If there's nothing obviously wrong, perhaps you could look at it on Friday zoom session?

Cheers
Oz

[ozaz]

I just bothered to look at the code in the network file and noticed a HEAP of these lines:

 <testpreset name="test mini tree">
    <channelr start="1" end="512"/>
  </testpreset>

No idea how they got in there.

Deleted them all from the xml file, reopened xlights, made a minor change (increased number of dmx channels) in setup and they are back! No wonder it takes so long to save. Files size increases from a few K to several M

OK this is a fairly serious issue (for me at least), hopefully one that is easily fixed by the clever developers

Edit:

Just created a brand new folder, added two networks , nothing else and saved. TaDa - hundreds of extra lines as per above.

On a side note, every time I open xlights since .35 two house preview windows open

[keithsw1111]

The issue here is significant duplication of test presets. It is not clear to me how they got there but I will include a change in .36 that will remove them.

[davidwill]

For Keith,
It seams that when xlights crashes for me it is just random. Not sure if these will help but here you go. Thanks you to all the developers for taking the time to help others when it is so close to having to deal with  there own displays.
David