Faulting module Qt5Core.dll
-
wrote on 26 Jul 2022, 18:18 last edited by
Hello,
We have developed an application that syncs between customer databases and it works on close to 100 computers except one, where we are getting the below error. Any insights would be greatly appreciated.
Faulting application name: Toboggan.exe, version: 2.8.0.0, time stamp: 0x62a24738
Faulting module name: Qt5Core.dll, version: 5.15.2.0, time stamp: 0x61d69156
Exception code: 0xc0000409
Fault offset: 0x0001f081
Faulting process id: 0x3194
Faulting application start time: 0x01d8a11808439164
Faulting application path: C:\ProgramData\Xactware\Toboggan\Toboggan.exe
Faulting module path: C:\Windows\TEMP_MEI26482\Qt5Core.dll
Report Id: e557b69a-3067-4f6b-afc5-fca506643e6a
Faulting package full name:
Faulting package-relative application ID: -
Hi and welcome to devnet,
Can you see if that machine has something drastically different from your other machines ?
For example different flavor of Windows, not the same service packs installed, a recent update, etc.
-
Faulting application path: C:\ProgramData\Xactware\Toboggan\Toboggan.exe
Faulting module path: C:\Windows\TEMP_MEI26482\Qt5Core.dllThis part looks weird. Are those paths correct? Usually Qt dlls would be deployed next to the exe.
Maybe that one machine has another incompatible version of Qt installed and added to PATH and that gets erroneously picked up instead of your version?Exception code: 0xc0000409
This is a stack buffer overrun exception. If the above paths and dll versions are ok then it seems like a bug in your app. Since the fault occurs in Qt dll I would suspect you're trying to use a Qt object that is already deleted or have a leak and you're recreating some object over and over and blow the stack. Something like that. If you can try running a debug version of your app on that machine and collect a crash dump. That would give you a callstack to look at to see where in your app the fault occurs.
Since you have a module name and fault offset you can also try to figure out what function crashes. Raymond Chen of Microsoft describes how to do that in his blog post.
-
Hi and welcome to devnet,
Can you see if that machine has something drastically different from your other machines ?
For example different flavor of Windows, not the same service packs installed, a recent update, etc.
-
wrote on 2 Aug 2022, 15:23 last edited by
@hskoglund thank you, they had WebRoot which did some changes, will check to see if Avast is running on it as well.
-
Faulting application path: C:\ProgramData\Xactware\Toboggan\Toboggan.exe
Faulting module path: C:\Windows\TEMP_MEI26482\Qt5Core.dllThis part looks weird. Are those paths correct? Usually Qt dlls would be deployed next to the exe.
Maybe that one machine has another incompatible version of Qt installed and added to PATH and that gets erroneously picked up instead of your version?Exception code: 0xc0000409
This is a stack buffer overrun exception. If the above paths and dll versions are ok then it seems like a bug in your app. Since the fault occurs in Qt dll I would suspect you're trying to use a Qt object that is already deleted or have a leak and you're recreating some object over and over and blow the stack. Something like that. If you can try running a debug version of your app on that machine and collect a crash dump. That would give you a callstack to look at to see where in your app the fault occurs.
Since you have a module name and fault offset you can also try to figure out what function crashes. Raymond Chen of Microsoft describes how to do that in his blog post.
wrote on 2 Aug 2022, 18:32 last edited by@Chris-Kawa thank you! That is what struck us as odd too, each time our app triggers off, QT is creating a new temp table and giving that message about the path being wrong. We have our app running on 95 other computers without issue except this one.
-
Hi @MartinF did you ever find a solution for this? I have the exact same error and exception code as you did and nothing I have tried has fixed this issue.
Please let me know!
wrote on 12 Apr 2023, 14:42 last edited by@DanMaccas Hi Dan, unfortunately no resolution as of yet. Have you had any success finding a solution?