Sean Meighan
Welcome => Latest xLights/Nutcracker software => Topic started by: amtrak115 on July 16, 2016, 02:16:32 PM
-
just got back from a road trip, downloaded .40; installed it then tried to load a sequence. xlights crashed. tried again and click on Layout tab, xlights crashed. redownloaded and reinstalled and tried to load a sequence again. Xlights crashed.
...
attached screen shot of xlights...cpp.log file
any thoughts or ideas??
Barry
-
Pls attach the crash dump or package up you log files using the tools menu and post them to us.
-
here the log files
-
So can you load the sequence at all. Both of the crashes I can see seem to be related to paste and undo. Not a sequence loading problem.
-
Here's the exact steps.......
lauch xlights....normal
click on sequence tab....Crash....
dialog attached......
Relauched xlights....normal
packaged log files....attached.
-
ok ... I now see what is going on. Its not actually crashing ... its actually hanging and windows is detecting that. I was looking for crashes in the logs.
I am going to speculate here ... I think it is a perspectives problem. I have attached a new rgbeffects file. Please backup your existing one then overwrite it with this one and see if it works.
-
no change
-
I can open up your show without errors. So were you running version 2016.39 successfully?
-
yes i was running fine with .39.
.40 has been flaky. one time it crashes as soon as I go to the sequence tab. next time I can click on sequence then open select a sequence then crash...next time pick a different sequence it loads and executes, pick the original sequence loads and executes...close everything out...crashes as soon as i select the sequence tab.
keith basically reset my perspectives back to default and that did not change anything.
just tried it again. select the sequence tab. the windows borders for all the different windows on the sequence tab (screenshot attached)
also attached the log files
-
I'm starting to wonder if I'm running into a graphics issue with the AMD Graphics card. I reloaded xlights .40 on an intel laptop and it worked fine. reloaded .40 on my amd home computer...and it fails as documented above. any thoughts on the AMD Graphics board ????
-
Once 41 is out, there are a bunch more debug settings I can give you to get more info in the logs related to the ATI stuff.
-
I'll probably need the debug switches...I just downloaded .41 and am still having the same issues. Tell me how to turn more detail debugging to the log and I'll send everything back
Barry
-
In the directory where the xLights.exe is found should be a xlights.windows.properties file. You need to edit that (notepad should be fine). Change the lines:
log4cpp.category.log_opengl=INFO, A1
log4cpp.category.log_opengl_trace=INFO, A1
to
log4cpp.category.log_opengl=DEBUG, A1
log4cpp.category.log_opengl_trace=DEBUG, A1
-
here's the log file after turn on those two debug items....
launched xlights.
clicked on "sequence" tab.
Crash....
-
Honestly, I have no idea... The wave form was created and all the GL data is sent to the card. The ONLY thing after this on the GL side of things is the SwapBuffers.
That said, I did see some "strange" values due to the timeline not being initialized. Can I ask a few questions:
1) If you go to the Layout tab, does that display?
2) If you open xlights and immediately open a sequence that includes audio BEFORE going to the sequence tab, does that work? That should have at least initialized the data that I was seeing being used before it was initialized.
-
1) If you go to the Layout tab, does that display?
When I clicked on Layout tab...it hesitated then crashed. (xlightsproblem8.zip)
2) If you open xlights and immediately open a sequence that includes audio BEFORE going to the sequence tab, does that work? That should have at least initialized the data that I was seeing being used before it was initialized.
opened a sequence immediately after starting xlights without clicking on anything else.. Crashed....
(xlightsproblem9.zip)
-
Wow. I really have no idea. There aren't any error return codes for any of the OpenGL calls. All of the drawing that WE do is supposedly succeeding. The only call after these is the wxWidgets SwapBuffer call. I really have no idea what to do to fix this.
Can you also try flipping to OpenGL 1.x and seeing if that helps?
-
Not only that but the crashes are not logging any information about the crash. The last crash in the log was on July 13 @ 4:30pm.
Since then it has crashed a lot without logging anything about the crash. Curiously on 23/7 @ 4:12pm it seemed to run normally ... for a while ... The autosave times are quite slow ... your J drive ... is it an old flash drive or a network drive?
-
j drive is a fairly new USB stick. When I entire J drive (usb stick) over to the hard drive. I got the same thing.
move the J drive to an intel laptop and it worked fine..that's was on .40 haven't tried .41 on laptop. Laptop is my wifes' that I'm stealing to go on a trip tomorrow.
-
I just stuck a xLights-Win-Test.zip file up on http://dankulp.com/xlights that contains some new DLL's and exe. It contains a little bit more logging and some minor fixes. Can you give those a try?
-
sure I can try that...also, went to the Windows Applications event log. attached is the details from the last error with xlights...
-
Dan/Keith...
I may have found the issue. if you look at the application event log that I sent the faulting module path is
c:\Progra~2\raptri~1\PlaysTV\......
I believe that is an application that is loaded as part of the AMD display driver set. once I removed that PLaystv app from my system everything appears to work. I'm going to reset everything back to .41 off the distribution site and try it again...
Barry
-
Ok, it appears that removing that app fixed the issue. I've started xlight 3 different time loaded a couple of sequences, played them then closed xlights. everything normal.
thanks for all your help
Barry
-
Nice find. Wonder how many other AMD users having issues have something like this being loaded.
-
maybe we should store a list of running programs into log file on a crash?