Crash after changing directory and creating new sequence

[Clyde-L]

Running version 2024.02 on Windows 10
Debug file attached
This crash occurred following these steps:

1 Change directory (permanent) from one layout to another. (I had previously been sequencing on that layout)
2 Clicked on "New Sequence" icon. (New sequence wizard opens up)
3 Clicked on "Musical Sequence"
4 Selected an Audio MP3
5 Clicked "20fps"
6 Clicked "done"
7 xLights starts to create the sequence, then I receive this crash report.

I do leave my computer running 24/7 and had stopped working in xLights at 2am last night. I resumed working on this instance of xLights at around 10:00am, and finished up something before switching the directories around 10:45am.

I've had this happen a number of times when working between directories. But it specifically happens when creating a new sequence after changing directories. After re-opening xLights, I can successfully create the new sequence.

The crash happens when I'm switching directories and just creating either a Musical or Animation sequence. This doesn't happen every time I change between directories then create a new sequence.

I notice that it happens "sometimes" when I have 2 instances of xLights open and I'm working between 2 sequences. If one of those instances is not used for a period of time, say 6 hours; that's when it potentially happens. I have tried to recreate the crash just now and not been able to. So, having an active session of xLights sit idle may have an effect?

Thank you for looking
Clyde L

xLights_dbgrpt-57292-20240208T105600.zip

[cybercop23]

Similar issue with the last error in #4277

Looking at the logs, the session that crashed was open for almosst 48 hours with other instances running at the same time and this being used. There are some last gaps in times during those hours and the next interactions worked... until it didn't.. but seems to be the same issue.. getting stuck on Perspectives... Did you by any chance disconnect monitors or the laptop in betwee?

[Clyde-L]

No monitor was disconnected. This was done on my main desktop, with 6 monitors.

I have experienced the same thing on my laptop in the past as well, having only the onboard monitor connected.

[derwin12]

Is this still an issue - @dkulp Dan I think caught a few crashes with a recent commit.
I cant duplicate it.

[Clyde-L]

Honestly I have not noticed anything in the past week. Did just upgrade to the latest xLights version. No crashing yet, but I will have a chance to test it out more over the next week or so. Can we keep this open for a bit now that this version seems stable enough to use?

Thanks for everything!

[derwin12]

Sure thing..

[dkulp]

From the stack trace, this is down in the AUI Manager (wxWidgets code) which I also see occasionally in the Mac stack traces. That said, I've never been able to reproduce it so very hard to figure out what the issue is.

[Clyde-L]

Well it has happened again. Just submitted the pop-up bug report and referenced this Bug Report. Using Windows 10, xLights Version 2024.05. Yes I'm not up on the latest but this is still happening. I've attached the zipfile.

Thanks,
Clyde

xLights_dbgrpt-71220-20240403T170114.zip

[AzGilrock]

Its that darn wxAuiManager again. I've had a couple crashes in the debugger when starting xLights that are wxWidgets issues as well. Some kind of timing thing because it was complaining about only being able to add one sizer to a frame or something like that and normally that should be a hard error not an intermittent one.