Sean Meighan
Software => Bugs in xLights/Nutcracker => Bugs (Please dont post here, soon to be deprecated) => Topic started by: JMHaro on April 22, 2016, 03:25:33 PM
-
I'm working on my first layout and xLights keeps locking up on me. I originally started with the release version which was working OK for me, but then I was wanting some of the newer built in models. So I updated to 2016.20 and again updated to 21 and still having the same problem on both these beta versions.
All I'm doing is changing several models that I had made copies of. They are all Single Colors. For each one that I'm changing I'm just changing the color, the Start Channel, and then the Name. I can do a couple of them but then the application locks up and goes "Not Responding" forcing me to shut it down and start over. I'm even clicking the save button after I change each one now so I'm at least only losing the last item I tried to change.
If you need anything from me let me know.
-
Why don't you avoid doing any copy/pastes in the Layout window and see if the problem goes away? If so then report back.
-
It had locked up on me sooo many times. But then of course right after I reported the issue, I was able to finish editing the remaining last 6 items without any problems. It has failed on me one time giving me the bug report file but otherwise it hasn't locked up for me since then.
When we get the crash report files, do we just post them here? I'll attach the two that I've gotten so far but if there is a more proper way of doing it, please let me know.
Thank you.
-
For some reason it's crashing while creating an Undo point so that you can undo your model changes. I'm not familiar with that part of the code yet.
-
I tried importing an xml file from my macbook pro from the Vegas training and all hell broke loos for one of my songs. It's the one I spent most of my time on in the hotel room converting from a LOR sequence to xLights. On my Macbook pro all is well but on my PC it locks my system up to the point I cannot even create a new sequence with that particular song. I did typical troubleshooting but no luck. Any other song okay. Even the MP4 of same Halloween song caused the issue.
Ron
-
I tried importing an xml file from my macbook pro from the Vegas training and all hell broke loos for one of my songs. It's the one I spent most of my time on in the hotel room converting from a LOR sequence to xLights. On my Macbook pro all is well but on my PC it locks my system up to the point I cannot even create a new sequence with that particular song. I did typical troubleshooting but no luck. Any other song okay. Even the MP4 of same Halloween song caused the issue.
Ron
From the backtrace: xLightsFrame::OnBitmapButtonSaveSeqClick
That tells me you clicked the Save button and then it crashed. You didn't describe it that way. So is that what happened?
-
I tried importing an xml file from my macbook pro from the Vegas training and all hell broke loos for one of my songs. It's the one I spent most of my time on in the hotel room converting from a LOR sequence to xLights. On my Macbook pro all is well but on my PC it locks my system up to the point I cannot even create a new sequence with that particular song. I did typical troubleshooting but no luck. Any other song okay. Even the MP4 of same Halloween song caused the issue.
Ron
From the backtrace: xLightsFrame::OnBitmapButtonSaveSeqClick
That tells me you clicked the Save button and then it crashed. You didn't describe it that way. So is that what happened?
Gil,
Sorry. Yes, that's when it crashes. It also crashes after about a second of playback.
Ron
Sent from my SM-G920V using Tapatalk
-
Do you have channels defined on your network setup page?
-
We shouldn't ever crash even when you have things setup wrong. I'm wondering if the crash is because you have a Matrix that ends on channel 152,073 and your network setup ends at channel 101,888. This is all based on what's saved in your crash report so if you added more channels without saving I wouldn't see them.
-
We shouldn't ever crash even when you have things setup wrong. I'm wondering if the crash is because you have a Matrix that ends on channel 152,073 and your network setup ends at channel 101,888. This is all based on what's saved in your crash report so if you added more channels without saving I wouldn't see them.
Actually the channels were less when I used a separate directory for Halloween. I deleted all the models I didn't need for Halloween show. Nothing overlapped. Again, it only happens with this song.
Sent from my SM-G920V using Tapatalk
-
I notice the sequence duration is almost 12 minutes and you have a 100,000+ channels so you will be using a ton of memory. Since this is only one that fails is it the longest? Is anything that works close to this length?
-
I notice the sequence duration is almost 12 minutes and you have a 100,000+ channels so you will be using a ton of memory. Since this is only one that fails is it the longest? Is anything that works close to this length?
Works fine on MacBook Pro. My custom built PC out powers the mac in memory and processing.
Sent from my SM-G920V using Tapatalk
-
I notice the sequence duration is almost 12 minutes and you have a 100,000+ channels so you will be using a ton of memory. Since this is only one that fails is it the longest? Is anything that works close to this length?
Sorry, needed to read you question again. No other sequence is this long. Originally in 2016.20 I created a new sequence with this audio on my MacBook Pro in class during our Vegas training. Later that evening I converted .lms show into xLights. The mapping was off but I was able to see the effects and save 12 minutes worth of effects for a given prop as a preset. I would then go to a new sequence with same audio, right click on timeline for a prop and add that effect. Worked like a charm. The show still runs fine on MacBook Pro. Fast forward to yesterday where I copied xml files to my pc and placed in my Halloween directory. The file opened and all effects were there along with audio. When I tried to save I crashesld. I tried the same thing rendering without saving, running from xmas directory, creating a new directory and always the same thing. I also went back to 2016.20 several times with various combinations.
When I get home I will try breaking the audio in sectionso to see if that makes a difference.
But in my mind just adding 12-13 minute audio file should not overtax the system to the point of a crash.
Worst case scenario- I can finish the Halloween show on my Mac. ;-)
Ron
Sent from my SM-G920V using Tapatalk
-
150K channels at 12minutes is about 2Gb of memory. With effects and caches and such, I could definitely see it being a problem on Windows (32bit) but work OK on the Mac/Linux (64bit).
-
150K channels at 12minutes is about 2Gb of memory. With effects and caches and such, I could definitely see it being a problem on Windows (32bit) but work OK on the Mac/Linux (64bit).
Running 24MB and i990x processor. Limitation addressing 32bit still an issue on my rig? Now I am intrigued.
Ron
Sent from my SM-G920V using Tapatalk
-
Yes a 32 bit application can only address a certain amount of memory. If you have more that only helps other applications.
-
Yes a 32 bit application can only address a certain amount of memory. If you have more that only helps other applications.
Excellent! So you are saying 2016.22 will be released as 64bit application? Hint hint... LOL
Sent from my SM-G920V using Tapatalk
-
Well... after much testing it is definitely the length of the audio. I cut it in half and that seems to work but way too much work to do it on the PC. Looks like my Halloween show will have to sequenced from my MacBook Pro. As long as my company doesn't take it away from me between now and Halloween no worries.
Ron
PS I really hope that xLights runs in 64bit mode one of these days. That would be a game changer for us pixel hogs.
-
Just quit trying to sequence Inagodadavida.
-
Just quit trying to sequence Inagodadavida.
That's actually good advice but it's too late for contingencies.
Sent from my SM-G920V using Tapatalk