Qt Application crashing at startup on some of the windows machines.

[Suresh Kumar]

Hi all,
I'm experiencing a strange problem. A qt application which upgraded with 6.2.2 crashing on some of the widows machines at production side. But on the same machines, application running which using Qt 5.

This is what I get from the Windows event data:

Source: Application error

Faulting application name: IDApplication.exe, version: 1.11.13.0, time stamp: 0x6213afb2
Faulting module name: Qt6WebEngineCore.dll, version: 6.2.2.0, time stamp: 0x619fabb2
Exception code: 0x80000003
Fault offset: 0x0000000001fe2a3b
Faulting process id: 0x80f0
Faulting application start time: 0x01d855b3b0b745cc
Faulting application path: C:\Program Files (x86)\IDApplication\IDApplication.exe
Faulting module path: C:\Program Files (x86)\IDApplication\Qt6WebEngineCore.dll
Report Id: 45ef3584-3050-407b-846f-123683e63d8f
Faulting package full name:
Faulting package-relative application ID:

Surprisingly, if I am running dependency walker and starting profiling then application running successfully.

Any clue what's happening around it?

[e.sinoheh]

Same here with version 6.9.2
Faulting module name: Qt6QuickTemplates2d.dll, version: 6.9.2.0, time stamp: 0x68a23c1c
Exception code: 0xc0000005
Fault offset: 0x00000000000357eb
Faulting process id: 0xEE94
Faulting application start time: 0x1DC2A4A105C4584

[ChrisW67]

@e.sinoheh Windows exception code 0xc0000005 is a generic "Access Violation". These usually arise because your program is using a pointer that is null, not initialized, or used after free. You may also get this result if you have mixed Qt library versions.

Run your program in a debugger until it crashes and obtain a stack backtrace. Read back through the backtrace until the first line of your code appears. The problem access is probably there.