Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: wftxlites on May 07, 2017, 05:46:51 PM
-
I am getting a Windows Blue Screen Crash when unchecking the output to lights in Test Lights. I believe this is related to another post I saw on a LOR Dongle with the same issue. However, it appears not to be isolated to LOR as I am using a Lynx USB Dongle (FTDI Version 2.12.26.0). This is a very repeatable crash. I also was able to duplicate from the Sequencer Output. I am at Xlights Version 2017.12 64 bit.
-
I was getting the same thing a while ago. If I remember I just erased all my setup and started over again. I was using a 16 ch LOR AC controller and a AlphaPix. I moved the LOR outputs to another spot. I also went back to the production release.
-
I think we know why this happens and hope to have a fix in .13
-
2017.13 did the trick. Tested and no crash!
Thank You
Greg
-
Well I spoke too soon. I left the xlights program running on my PC the last couple of days idol and then resumed testing various effects in the sequencer to observe my rgb test light string. There seems to be a lag in the sequencer while changing an effect and while the output is on. It seems the DMX output to the dongle is laging the change made to an effect by literally seconds. So I decided to stop the output and see how long it took for the test lights to go off. Boom it crashed the PC. I have seen this lagging behavior before but didn't think too much about it while playing a sequence with the output on. Now, I think these two observations could be related to the crash. I hope this is useful info to determine the exact cause.
Possibly this is a memory leak because after restarting the PC and restarting the program everything seems fine doing the same tests.
-
I need to see crash logs.
-
The crash is likely occuring because in the 50ms we give the serial port to finish transmitting it didn't manage to do so.
No idea at this stage why it gets slower over time.
-
Searched the entire HD and only crash files are from older versions a year or more ago. Not the same crash issues either. Sorry no crash logs were generated by xlights due to the "Blue Screen of Death Crash". I suspect no time for Xlights to gen them. Let me know anything else I can do to help.
-
Not much because a blue screen crash is occurring inside the USB device driver not inside xLights. If the driver was written well it should never be able to crash no matter what we send it.
-
All the more reason to completely ditch LOR.
Sent from my Pixel using Tapatalk
-
All the more reason to completely ditch LOR.
Sent from my Pixel using Tapatalk
That's what I did, I ditched everything LOR.
Spent a month reworking everything so I didn't have to bring anything in it as a data layer
-
All the more reason to completely ditch LOR.
Sent from my Pixel using Tapatalk
That's what I did, I ditched everything LOR.
Spent a month reworking everything so I didn't have to bring anything in it as a data layer
I bet you are a happier person for it, right? 😀
Sent from my Pixel using Tapatalk
-
I just pulled out my LOR 16 channel AC controller and ran it with a LOR USB 485 Isolated Adapter. Its the black version with 2 ethernet style outputs and USB input. Just wanted to make sure Keith's change didn't break the blue screen crash that was fixed previously and it did not.
My question is does everything work fine initially like can you run an effect on the grid and turn Output to Lights on and off a few times without a crash? Turning it off used to cause a blue screen crash every time till we put in a short delay when closing the connection to the driver.
-
With the latest ver. 2017.13 yes. With 2017.12 crash every time.
-
All the more reason to completely ditch LOR.
Sent from my Pixel using Tapatalk
That's what I did, I ditched everything LOR.
Spent a month reworking everything so I didn't have to bring anything in it as a data layer
I bet you are a happier person for it, right? 😀
Sent from my Pixel using Tapatalk
Yep. ;D
-
It's not just LOR. I am using DLA USBD.
-
With the latest ver. 2017.13 yes. With 2017.12 crash every time.
So the only crash you got now was after running it for a couple days. Kinda hard to troubleshoot that.
-
There may be a way to purge pending data.