2.0.00 and 2.0.01 crash

[Yann (Yannick)]

Hello !
I have upgraded 3 computer with 2.0.00 then 2.0.01 (Win 11)

Two computer are OK, but third one refuse to start Lightburn.

Here is the log:

Crash Log Stack Trace for LightBurn v2.0.00:

QAction::setEnabled
EditWindow::vector deleting destructor' QObjectPrivate::deleteChildren QWidget::~QWidget QWidget::vector deleting destructor’
QObjectPrivate::deleteChildren
QWidget::~QWidget
_CxxFrameHandler4
<couldn’t map PC to fn name>
<couldn’t map PC to fn name>
<couldn’t map PC to fn name>
<couldn’t map PC to fn name>
_CxxFrameHandler4
_chkstk
RtlUnwindEx
_C_specific_handler

Undo Stack:

Redo Stack:

Any idea ?

Thanks !

[Yann (Yannick)]

Hello,
upgraded to 2.0.02, still same issue !!!
Check VC++ Redist → OK

No clues… Could someone from dev help ???

[JohnJohn (John Johnson)]

Thank you for reporting this.

Something similar came up in a support team meeting today. Your profile says that your computers are running Windows 7, 10 & 11. Qt6 builds ( the tool the Dev team uses to build LightBurn) don’t offer support for Windows 7 systems. There’s also a minimum Windows 10 OS revision-level requirement. I’ll find it and share it here.

[edit: Windows 10 build 1809]

I’d like to know more about the computer that is crashing. Which operating system is on the computer that isn’t launching LightBurn? (If Windows 10, what is the current revision number?).

Is it an older computer with a possibility of having a 32-bit CPU?

[Yann (Yannick)]

Hello,
Oh yes, Win7 computer on my profile is not used anymore for LB.

The faulty computer is a Win11 (64bits, no 32 available for W11) without any ‘strange’ software installed on it.

2.0.xx refuses to start, but reverting to 1.7.xx is OK.

Today I have updated to 24H2, I will check tonight if things are improving or not.

I can give you more informations if needed.

Rgds.

[Yann (Yannick)]

Hello,

Tested again with this computer: Win11, all up to date.

Started as admin or not, 2.0.00,01,02 crashes as usual…

I’m really stuck ;-(