Two folks saying .11 wont start in Windows ..

[derwin12]

The logo shows (atleast 1 user is dark mode) then quits. Not sure how to troubleshoot. Going to rollback to .10 and see if log shows anything.

(works fine for me btw). Daryl.

[derwin12]

Crashing after the GL panel

[derwin12]

xLightsProblem.zip

[derwin12]

Tried /w .. still not working. Crashing on this. This is from my log .. it doesnt appear in the reporting user's log (Joe).

**"2024-06-15 20:13:00,040 29484 log_base [DEBUG] Effect assist."**

[derwin12]

Ron R. crashed in a slightly different spot...

[AzGilrock]

Those highlighted sections don’t look like crashes.

[derwin12]

Yea no crash dump just stops.

On Sat, Jun 15, 2024, 8:44 PM Gil Jones @.***> wrote:

Those highlighted sections don’t look like crashes.

— Reply to this email directly, view it on GitHub https://github.com/xLightsSequencer/xLights/issues/4617#issuecomment-2170993471, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDNVK7PRZYDUDD6W2KZPRDZHTNVFAVCNFSM6AAAAABJMCNPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZQHE4TGNBXGE . You are receiving this because you authored the thread.Message ID: @.***>

[derwin12]

Third one reported..

On Sat, Jun 15, 2024, 9:04 PM Daryl Erwin @.***> wrote:

Yea no crash dump just stops.

On Sat, Jun 15, 2024, 8:44 PM Gil Jones @.***> wrote:

Those highlighted sections don’t look like crashes.

— Reply to this email directly, view it on GitHub https://github.com/xLightsSequencer/xLights/issues/4617#issuecomment-2170993471, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDNVK7PRZYDUDD6W2KZPRDZHTNVFAVCNFSM6AAAAABJMCNPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZQHE4TGNBXGE . You are receiving this because you authored the thread.Message ID: @.***>

[computergeek1507]

If you have someone that doesn't work on 11 do a package sequence on 10 and upload it

[derwin12]

The package logs was from 10. I think two of them were on 10. I am on 10 without issue.

On Sat, Jun 15, 2024, 9:09 PM Scott Hanson @.***> wrote:

If you have someone that doesn't work on 11 do a package sequence on 10 and upload it

— Reply to this email directly, view it on GitHub https://github.com/xLightsSequencer/xLights/issues/4617#issuecomment-2170998252, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDNVK6DBY6TUNVBXKSYMGLZHTQT3AVCNFSM6AAAAABJMCNPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZQHE4TQMRVGI . You are receiving this because you authored the thread.Message ID: @.***>

[xlights33]

2024.10.zip This is a test sequences packaged from 2024.10 (Joe)

[blun23]

I'm on the TestFlight on Mac and I am having issues saving a sequence. Beachball is just spinning after doing the latest update. Way longer than usual.

[derwin12]

Duplicate #4618

[geoffhoops]

I am having the same problem with the new version .11. The logo flashes up briefly then nothing. the Scheduler and Scanner do exactly the same, nothing happens. Go back to version .10 and everything is fine. reinstall .11 and nothing happens again.

[keithsw1111]

2024.10.zip This is a test sequences packaged from 2024.10 (Joe)

Downloaded and opened your sequence

So if the crash is not specific to your show folder it is going to be down to settings or something else environmental. The only way to troubleshoot may be builds with additional debugging until we isolate the issue.

Looking at the log above in daryls post there is a lot that happens after that log message. In my log the first thing i see is a message about the download cache ... purging the download cache in .10 and re-upgrading to 11 may help ... but equally may not.

[derwin12]

Folks having problems, could you verify that this nightly works No. 924 https://github.com/xLightsSequencer/xLights/actions/runs/9378451618 And this one does not.. No. 925 https://github.com/xLightsSequencer/xLights/actions/runs/9395371749

[AzGilrock]

Even if it appears that commit is where it broke I can't see how its that code that broke it. It makes me think its more likely to be a case where there's bad code somewhere else that stomps on something and this change just shifted around the code that gets stomped on into something that has a worse reaction. If it really was this code the only thing that seems possible is the creation of the canvas object failed and its a null pointer. Could add a null check to this just to test but again adding the null check could potentially shift other code around and make us think its fixed when all we did was shift where a bad pointer is writing.

[derwin12]

Agree ,.. but need to start somewhere. Ideally we get a second or third confirmation on these commits. Then put in some debugging and track it down.

[derwin12]

Gil - is your code blocks older? Curious that when I just open the mhpanel, it updated with the following changes. Could wxWindowID vs long be an issue? (we dont get a core dump though)

[AzGilrock]

Yeah its highly possible my CodeBlocks is older. There's not really any announcement when one of the guys changes the version so its easy to be behind until a problem reveals itself. I seem to remember running version 16.

[xlights33]

Folks having problems, could you verify that this nightly works No. 924 https://github.com/xLightsSequencer/xLights/actions/runs/9378451618 And this one does not.. No. 925 https://github.com/xLightsSequencer/xLights/actions/runs/9395371749

924 worked
925 same as 2024.11 just flash startup screen

[computergeek1507]

924 was build using the 20240511 Windows github action image, which used the VS2022 17.9 MSBuild compiler. 925 used the newer 20240603 Windows github action image, which used the VS2022 17.10 MSBuild compiler. Maybe a optimization bug in VS2022 17.10. If Keith used 17.10 his release may have the same issue.

[computergeek1507]

try installing the newest C++ Redistributable with VS 17.10/ C++14.40 support

https://aka.ms/vs/17/release/vc_redist.x64.exe