Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: danj on May 13, 2015, 08:49:58 PM
-
I have gotten multiple crashes tonight when using 4.0.30; probably on the order of 20 or so==crashing pretty much every time I am in the sequencer. xl4 gives me the debug report screen and shuts itself down. Here are a few of the debug report files. If it makes any difference what I am "doing", I am in the sequencer each time and sequencing AC models. I am not seeing any cause/effect... Sometimes it crashes when I copy/paste, sometimes when I am setting effects, other times when I am saving. Always when I am in the sequencer, though...
-
I've been getting way more crashes with the last two releases too. I will get them when I'm working in the sequence grid as well, and when clicking from cell to cell or trying to copy and paste at times. The one thing I cannot locate though is the debug report that says is being generated. I've searched my entire system for anything related to xLights in the file name and it comes up with nothing, so I have no clue where the reports are going. If it's worth anything, I'm running the Mac version.
-
Kevin:
I am running windows PC with windows 7. xlights is putting the debug reports in the "target folder" show directory I have setup in xlights. Here is a typical debug folder title: xLights_dbgrpt-6052-20150513T224436
-
danj's sequences have a bunch of Text effects. kevin: when it's crashing, do you have a bunch of text effects?
I just committed a change that I HOPE will help. Text effects have to be rendered on the main thread due to using the OS rendering calls to get the text information and render the text and such. Thus, we pop a message on the main thread to have it do it's thing. We had a timeout in there of 1/2 a second (that's per frame BTW) at which point it would continue on. However, I kind of realized that if it continues on, it's pretty much guaranteed to crash. Thus, I just removed the timeout. On slower machines, maybe it does take longer to render than I expected. Don't really know.
-
Kevin:
When the dialog pops up, make sure you hit the OK button and not the cancel button. If you hit the cancel button, no report is generated. When you hit OK, it SHOULD be in your show directory.
In anycase, when the dialog is open, if you click on the View button or the Open button for the backtrace.txt, you should be able to see the backtrace and copy/paste it elsewhere.
-
Dan---I just opened another sequence file that does not have any text effects in it and I got a crash there too.
Here are those debug files.
-
Thanks for the info guys. I will make sure to click OK and see if that helps with my issue of not seeing the reports. As for text effects in the sequence, I only have one, and that's at the very end. I wasn't even close in the grid to that effect when it crashed. I will try to replicate it tomorrow and post the report.
-
Still getting Crashes when converting lms files.
I have attached the zip file I bought and a couple of the bug reports.
I am running Windows 7.
Please do NOT download this file for use in a sequence, please buy your own from www.holidaysequences.com and support the ppl who develop these.
-
Like Kevinp when coping and pasting several times xl4 crashes. I can recreate it by creating a new sequence, having one model, 4 timing marks, put an effect in the first timing mark, copy and paste three times, on the third paste xl4 crashes. On on one crash, the debug box showed 3 times and I couldn't do anything but end task.
-
Like Kevinp when coping and pasting several times xl4 crashes. I can recreate it by creating a new sequence, having one model, 4 timing marks, put an effect in the first timing mark, copy and paste three times, on the third paste xl4 crashes. On on one crash, the debug box showed 3 times and I couldn't do anything but end task.
buzzdude, that is very specific set of steps - Did you not get that crash in 4.0.29 ??
Something that has helped others in the past (don't know why, but ..) is to just Reinstall 4.0.30. Then reboot the computer.
-
There was hardly any changes in this release that would have improved any of the existing crashing problems that I can see. I think the release notes included a lot of closed issues that had already been closed by previous releases and not this specific release when I compare the list to the checkins.
I'm just not able to spend a lot of time to help Dan find these issues for the next week because I've been scrambling to get hardware and sequences ready for a high school graduation party where I'm displaying a 50x12 horizontal ribbon matrix and a 32x42 matrix using my pixel straps. This is a big event they do every year to try to keep the kids from going out driving unsafe and killing themselves. It's pretty amazing the setup they create. This year its a Vegas theme. They have prizes that provide a big incentive for the kids to show up like they give away a car and I think a $2000 prize in a raffle. The kids are not allowed to leave until sometime early morning once they enter.
-
Kevin,
I just stuck a new 4.0.30a build up for the Mac. Can you give that a try and see if that makes it more stable. I found some un-initialized variables that could cause it to render outside the proper range (like negative frame numbers) the would easily cause crashes.
-
Thanks Dan. I'll download it when I get home from work this afternoon and give it a try. I'll keep you posted.
-
Ok, now I'm getting crashes in 4.0.30. It seems cumulative. Works well until you save for the 3rd or 4th time.
the sequence has no Text effects at all
-
Like Kevinp when coping and pasting several times xl4 crashes. I can recreate it by creating a new sequence, having one model, 4 timing marks, put an effect in the first timing mark, copy and paste three times, on the third paste xl4 crashes. On on one crash, the debug box showed 3 times and I couldn't do anything but end task.
buzzdude, that is very specific set of steps - Did you not get that crash in 4.0.29 ??
Something that has helped others in the past (don't know why, but ..) is to just Reinstall 4.0.30. Then reboot the computer.
Hi, I had skipped 4.0.29, so the issue only commenced for me in 4.0.30. I reinstalled and rebooted as you have suggested, but issue still remains. I also get the two debug reports, one on top of the other, the second one (all the text is bolded). I have also attempted to render after two consecutive pastes, but as soon I press the render icon, a crash report creates.
I have noticed that the timing marks I'm pasting into are slightly smaller that the original copied item, if that helps.
Thanks
Shane
-
Dan,
I found two of the backtrace files from crashes I was having yesterday. I've downloaded version 4.0.30a that you posted today and will let you know if I'm getting random crashes in the grid sequencer like I was yesterday.
[attachment deleted by admin]
-
Running 4.0.31. Was able to sequence for about 10 minutes using the same file as last night without problems until the very last time I saved the file. Debug report attached.
Thanks very very much to the dev team for working on this awesome sequencer.
Can't thank you enough.
-
Hi
Using 4.0.0.31, has fixed my problem, I have been able to copy and paste 17 effects over 4 timing marks and paste 15 times without an issue, also rendering without a problem.
Thanks, Guys
Shane
-
THANK YOU GUYS SOOOOOO MUCH. Converted lsp singing faces to xL4 and NO CRASHES using 4.0.31.
-
Running 4.0.31. Was able to sequence for about 10 minutes using the same file as last night without problems until the very last time I saved the file. Debug report attached.
Thanks very very much to the dev team for working on this awesome sequencer.
Can't thank you enough.
It might be totally unrelated but there are a few problems in the "Imported Timing" marks. If this was a sequence that you converted from V3 then it's possible it can contain problems if you converted it several weeks or months ago because we've made fixes to the conversion process along the way and we don't have code to fix up problems that could have occurred to XML files if they were converted during the beta stages.
You could manually edit the XML to clean it up. The timings for effects or timing marks should always have some amount of length meaning start and end times should never be the same. Start and end times should never be backwards. Timing mark ranges should never overlap. So if you look at this section below from your XML you have two timing marks that start and end on 20.0 and the one in the middle goes backwards in time. That could have been caused back when we had import problems.
<Effect label="snowflakes" startTime="20.000000" endTime="20.000000" />
<Effect label="" startTime="20.000000" endTime="0.050000" />
<Effect label="" startTime="20.000000" endTime="20.000000" />
This also makes me realize we probably don't have checks in there to make sure any text timing files you import don't have bad durations or ranges in the text file.
-
Gil--I tried what you suggested and I believe that is working. I haven't gotten any crashes for a while now, ever since I found & changed several start/end times that were the same or where the end time was before the start time...
THANKS SO MUCH!!!! I know what to look for if I am getting crashes now....
Edit--I am getting crashes "every once in a while" now that I have cleared out incorrect start/end timings. It is very tedious to go thru all of them, so I suspect I probably still have a couple in there getting me sometimes but not very frequently.
Interestingly, even though I had corrected a 20.0000 second start/end timing in the xml file, when I got several more crashes, I found that the line I had corrected had (I am guessing here..) overwritten such that the 20.0000 seconds was once again set for start/end... I looked at the sequence to see what was going on in that timeframe and found that I had a couple of timing marks in that area. I deleted those, as I didn't need them anymore. I think that solved this one...
-
Just a comment from the "banana gallery"....
I started having multiple crashes starting with 4.0.30 when copying/pasting a text effect. These were on a fresh sequence with no import of timing marks. It seemed to happen after a few copy/pastes. It got so bad that even if I clicked on an existing effect it crashed the whole program.
I've upgraded to 4.0.31 and I've only had 1 crash since then....
One thing I do notice is that in 4.0.30 when I copied and pasted an effect the length of the timing marks would be different in the location that I pasted to so I had to adjust the length on each pasted effect manually. In 4.0.31 when I copy and paste the length is the same....and as long as I place the cursor precisely at the right point it now pastes the effect in the correct location and for the right length.....
UPDATE: Well I spoke too soon....After rereading this thread and seeing the references again to multiple copy/paste's I went and did multiple copy/pastes....and when I tried to exit, and not even a save, I got another crash.
UPDATE 2: Hmmmmm, I went back and tried again to copy/paste multiple effects. I was successful and did dozens of them with no crashes. I did it exactly the same (Ctrl C/V) as the first time and it worked.... I made no other changes at all....went straight to copy/paste of effects that were previously saved on 1 model and other than it taking a quite a while to do all those copy/paste operations everything worked.....It plays....So I have no idea why the earlier crash happened. Gremlins maybe! ;)
-
Still getting crashes with 4.0.31 (same file as yesterday). I am going through the xml file and trying to correct all the timing issues. I might still have some I haven't found. I have gone over the xml file several times and I have found timing problems pretty much each time I have looked. Very tedious... I attached the debug files.
Edit: I am walking through all my files, as I found some for which I had not setup properly==LOR import data & render mode canvas. When I am trying to open up one of my files (has imported LOR data and xl3 imported data/timings), xlights crashes & gives me a debug report. I attached that debug report, too.
[attachment deleted by admin]
-
In regards to my last post, I pulled up an xml file from my most recent "backup" folder and it works fine. It is missing one effect right at the end but I can add that in like five minutes. Just thought I would update.
-
You have it set as a sequence type of Media, but there isn't any music/song set in the file. It's trying to load the MP3 and failing. We definitely should guard against that.
-
I am running 4.0.32. Any ideas as to what I should do with this file? I really want to keep what I have done with it!! I am getting crash/debug during the save process. I attached the debug report.
THANKS.
-
I tried your file and got it to preview and save but I didn't have the ISEQ file for the data layer so I had to delete that from the sequence. Hard to tell what's wrong from that backtrace. Just shows something going wrong inside a render job thread.
-
thanks for looking Gil. I pulled up a different backup file (thank goodness for BACKUPS!!!) and got it to work ok. So far anyway... Something about that file is just giving xlights fits for some reason....
-
One thing that concerns me:
<Effect ref="55" name="Color Wash" id="60" startTime="184.000000" endTime="184.050000" palette="43"/>
<Effect ref="43" name="Color Wash" id="0" startTime="184.000000" endTime="205.800000" palette="38"/>
Two effects on the same layer at the same starting time? That's not a good sign. Any idea how these effects were created? Import from v3? Import from LMS?
-
One thing that concerns me:
<Effect ref="55" name="Color Wash" id="60" startTime="184.000000" endTime="184.050000" palette="43"/>
<Effect ref="43" name="Color Wash" id="0" startTime="184.000000" endTime="205.800000" palette="38"/>
Two effects on the same layer at the same starting time? That's not a good sign. Any idea how these effects were created? Import from v3? Import from LMS?
I haven't read this entire thread, but to just reply to this last question, Superstar will allow same layer at the same time, also with the same name.
-
Yeah but our import code does a check and if an effect is already present we create a new layer and put the effect on a different layer. So we need to know if there is a boundary condition that causes the check to fail.
-
Dan---roundabout answer--I developed all my NC effects in XL/NC in 2013 then exported over to LOR. So, the existing effects on this particular sequence were imported back into XL from LOR... But from XL to LOR originally... In 2013 I had the concept I needed to run everything from LOR. I wish I had known then how easy it is to XL to schedule... Oh well!!
-
I am in the process of doing the "import effects" per Dan Kulp's video. I saved the mapping file then rendered and tried to modify the effects on the nodes I had mapped. I probably need to get all nodes mapped before I try this... Anyway, when I tried to save this file I got a crash. Here is the debug report.
Thanks for all the work all you developers are doing. Your efforts are very much appreciated!!