@JDePedro
Ok. I found the cause why I was not getting anything QML related from the tool. My widget is not in the exe file but in a DLL so I had to specify the dll instead.

But the list of files the tool is getting is huge compared with the one I got by doing the process "manually" and includes most of the .qml files. So my doubt is, do we need to deploy all this files with my application? is not enough with the dlls???

What does Deleaker do that Heob does not? I use Heob for memory leaks, but I don't know much more than that. I also use Valgrind for Linux, and I know it does more than Heob.

Hi @ivec

Is it normal that I needed to select the compiler manually?

No. but please select the C compiler also.

And how can I enable the use of a debugger to step through my program?

You need to install the Debugging Tools for Windows, included in the Windows SDK. Due to licencing, this is not possible otherwise.

Regards

@JonB Noooo... I did not understand that the enumeration of multiple paths in the Windows example referred to a list. Now I know :o) thanks.

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

This address is rather suspicious. Please tell me you don't have global QWidgets?

No, I have only a dll with function

extern "C" CORE_SHARED_API QMainWindow * svCreateMainWindow() { return new MainWindow; }

(CORE_SHARED_API is __declspec(dllexport))

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

Btw, 0xc0000409 is stack overflow, so be on the lookout for endless recursion.

As I said, QWindowsGuiEventDispatcher::processEvents() is called twice, and I believe those calls are on the same stack level (crush happens in the second call).

what is your suggestion about server app design ?

People usually refer to "server app" as "middleware" or "web application". There are tons of web frameworks and ORMs for various languages including Java and C# on "enterprise" side and scripting languages (pphp, python, perl, ruby, node.js). C++ is not really convenient language here. As for protocol, if you are not pursuing real-time data processing with lowest possible latency, it makes sense to use REST API on top of HTTP, so that on server side you have the most typical "web app" with ORM inside and REST outside, and on client side you can easily add web client if needed, and even if not, you get some additional convenience as compared to e.g. RPC over plain TCP

Hi,

An educated guess is that the second case is handled by the window manager (the decoration is not done by Qt).

One possible thing to do would be to check the screen resolution in your method and try to adapt to that.

@smhrambo deleting the *.pro.user file often helps when you do such moves...

@SGaist Thank you inform about me QtSingleApplication class. I will modify code and use QtSingleApplication.

There is a way to force an external window to become part of a widget, but the API isn't really meant to be used this way and there are multiple issues: https://bugreports.qt.io/browse/QTBUG-45275

@wrekler
ok. Im not sure what system buttons are.
But yes, its most likely there are bugs as its pretty involving across
platforms to support such decoration less window.

@JonB sorry for long reply
debug size is 29.5M
release size is 18.3M
Free memory always a more than needed PC have 16Gb ram. Also i checked swap, swap is newer used for last days. So problem is not here.
Next step i will check all dlls one by one in tes Win32 pure C application, maybe problem is here.

no cpecific initial code ... but as u can see a lot of dependencies.. In linux exist LD_PRELOAD key but there is no solution for windows i found.

Thanks for response, if i found any solution or reason i'll report it here.
Cheers.

@Natalya if your issue is solved, please don't forget to mark your post as such. Thanks.

For sake of completeness here is the answer from Qt developers (in case someone reads this and has the same issue):
http://lists.qt-project.org/pipermail/development/2018-April/032630.html

Unfortunately the reason why it was done in that way is still a mystery but it seems that the hook code can be safely removed

@aha_1980 i cleaned my old project build tried it again. The build is successful but when i try to run same error as mentioned above.

any changes : just uninstalled Qt5.9.1 .other than that nothing much.

this is my compiler tab if it helps any !!

p.. i have downloaded windows 10 SDK too now there is no triangle on msvc 32bit one but the problem still remains :/ .

Could you show full output of cmake? Did you install libsqlite3-dev package and cmake reports that sqlite is not found? That does not make any sense

Hi
Do you really need that many kits installed ??

Desktop QT 5.6.2 MinGW 32bit -> can make normal win32 apps in 32 bit. Run on win 10 64 bit too ( as 32 bit)
Desktop QT 5.6.2 MSVC2013 32bit. -> 32 bit, you must install compiler yourself. VS 2013 ONLY ( runs on 64 bit too)
Desktop QT 5.6.2 MSVC2013 64bit -> 64 bit, you must install compiler yourself. VS 2013 ONLY ( runs ONLY 64 bit )
Desktop QT 5.6.2 MSVC2015 32bit -> 32 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs on 64 bit too)
Desktop QT 5.6.2 MSVC2015 64bit -> 64 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs ONLY on 64 bit)
Desktop QT 5.6.2 for Universal Windows Patform 32bit Not a Desktop app. WinRT only app
Desktop QT 5.6.2 for Universal Windows Patform 64bit Not a Desktop app. WinRT only app

Sounds to me you can just use mingw. for both 32/64 bit unless you want app to be 64 bit ?

@raven-worx
I have also test the Registry Key changes, but doesn't have any impact.
By the way, I just realize that the XP build of my application is using ANGLE (because OpenGL is not supported) and Windows7 is using OpenGL.
By forcing Windows7 to use ANGLE, TeamViewer is working also with Windows7 :)

QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); qputenv("QT_OPENGL", "angle"); qputenv("QT_ANGLE_PLATFORM", "d3d9");

Thanks a lot for your time

Regards

For example: QCameraImageProcessing

@VRonin said in QCA no Makefile:

also, if you are using MSVC you have to tell cmake to generate makefiles instead of project files. Pass the -G "NMake Makefiles" arguments to your cmake call

You sir, have saved me. I can't believe they don't specify that in the guide (it also uses MSVC, so idk why there wasn't the same problem).

I've run into some trouble while building, but that can/should be its own topic.

@VRonin said in QCA no Makefile:

Slightly related, is QCA supported and updated? The last thing you'd want is to use an out of date cryptographic library.

I normally use Crypto++ but libcrypto of OpenSSL is also very good (if you don't mind messing with C)

It is still active, looking at the the git (https://cgit.kde.org/qca.git/) the last commit was in 2017-09-30 (some months ago, but it isn't dead).
I had also been looking at Crypto++, but ended up settleing for QCA for no pacticular reasons. And I wouldn't mess with C, I'm still even just a C++ newbie afterall ;) QCA can also use OpenSSL btw.

Hello

I can't try with webview because i don't use QML in my project.

If I load the flash applet into Google Chrome, or Windows ActiveX Flash component, it works perfectly. :(

@kshegunov said in qmake install error detection on Windows:

target.depends = baseLibs

This was a very promising idea but unfortunately it looks like .depends does not work with other INSTALLS tagets

Hi,

One small correction: you can use Visual Studio 2017 with libraries built for VS2015, these two compilers are compatible (which is the first time two Microsoft Compilers are compatible).

Replying to myself:

The bugrepport said is is fixed for 5.10.1

https://bugreports.qt.io/browse/QTBUG-64121

And it can be made to work with correct folder permissions :

$ ls -ld /etc/config/ drwxr-xr-x 2 root root 4096 avril 1 11:15 /etc/config/ $ sudo chgrp pi /etc/config/ $ sudo chmod g+w /etc/config/ $ ls -ld /etc/cleandrop/ drwxrwxr-x 2 root pi 4096 avril 1 11:15 /etc/config/

resolving simlink doesn't helps

// resolve symlink // https://bugreports.qt.io/browse/QTBUG-64121 QFileInfo info(_configuration_file); if (info.isSymLink()) _configuration_file = info.symLinkTarget();

So I removed this fix, and fixed the folder permission and it worked.

@kshegunov Thank you for your suggestion I will try to follow it.

@mrjj

Ok. I have fixed it temporary by defining in the .pro file:
DEFINES += _ATL_NATIVE_INITIALIZATION

And also reported it https://bugreports.qt.io/browse/QTBUG-63772 . Thank you.

Nobody has replied, so I've entered it as a bug: https://bugreports.qt.io/browse/QTBUG-63901. I'll see what happens.

Nowadays the software renderer for WebGL works fine. I wonder if there is some easy way to detect if the video adapter is affected (probably intel && being "old") and if that's the case, to switch to software renderer, at run-time - maybe before initializing QApplication? in order to pass --enable-webgl-software-rendering parameter programmatically.

I've been digging around for the last couple of days trying to find the root cause of the issue and then it turned out that even the simplest Qt Quick application will crash with the same stack trace as long as it displays some text. Likewise none of the examples that are shipped with Qt (accessible through the Welcome -> Examples screen in Qt Creator) work, they simply crash on startup.

Would it be safe to assume it's a bug with Qt 5.9.1 built using MSVS 2017 (VC14.1)?
How do I even proceed now? Do I report it on the issue tracker?

Here's the relevant backtrace:

. 0 Id: 24f8.dac Suspend: 1 Teb: 000007ff`fffde000 Unfrozen Child-SP RetAddr Call Site 00000000`0029df90 000007fe`ff58ab87 KERNELBASE!RaiseException+0x3d 00000000`0029e060 000007fe`ec6a865d msvcrt!CxxThrowException+0x87 00000000`0029e0d0 000007fe`e658ef00 dwrite!DWriteCreateFactory+0x3f51 00000000`0029e150 000007fe`e658fecb qwindowsd!createDirectWriteFactory(struct IDWriteFactory ** factory = 0x00000000`040a7428)+0x90 [c:\users\qt\work\qt\qtbase\src\platformsupport\fontdatabases\windows\qwindowsfontdatabase.cpp @ 103] 00000000`0029e190 000007fe`e658ce92 qwindowsd!initDirectWrite(class QWindowsFontEngineData * d = 0x00000000`040a7010)+0x2b [c:\users\qt\work\qt\qtbase\src\platformsupport\fontdatabases\windows\qwindowsfontdatabase.cpp @ 653] 00000000`0029e1e0 000007fe`e658b060 qwindowsd!QWindowsFontDatabase::createEngine(struct QFontDef * request = 0x00000000`0029e760, class QString * faceName = 0x00000000`0029e640, int dpi = 96, class QSharedPointer<QWindowsFontEngineData> * data = 0x00000000`0029e678)+0x1d2 [c:\users\qt\work\qt\qtbase\src\platformsupport\fontdatabases\windows\qwindowsfontdatabase.cpp @ 1888] 00000000`0029e600 000007fe`e6d4dedc qwindowsd!QWindowsFontDatabase::fontEngine(struct QFontDef * fontDef = 0x00000000`0029e760, void * handle = 0x00000000`00000000)+0x60 [c:\users\qt\work\qt\qtbase\src\platformsupport\fontdatabases\windows\qwindowsfontdatabase.cpp @ 1247] 00000000`0029e6c0 000007fe`e6d4e0f8 Qt5Guid!loadSingleEngine(int script = 2, struct QFontDef * request = 0x00000000`0029eba0, struct QtFontFamily * family = 0x00000000`04117820, struct QtFontFoundry * foundry = 0x00000000`0411b790, struct QtFontStyle * style = 0x00000000`0411b8c0, struct QtFontSize * size = 0x00000000`0411b950)+0x3dc [c:\users\qt\work\qt\qtbase\src\gui\text\qfontdatabase.cpp @ 971] 00000000`0029e820 000007fe`e6d49704 Qt5Guid!loadEngine(int script = 2, struct QFontDef * request = 0x00000000`0029eba0, struct QtFontFamily * family = 0x00000000`04117820, struct QtFontFoundry * foundry = 0x00000000`0411b790, struct QtFontStyle * style = 0x00000000`0411b8c0, struct QtFontSize * size = 0x00000000`0411b950)+0x58 [c:\users\qt\work\qt\qtbase\src\gui\text\qfontdatabase.cpp @ 1000] 00000000`0029e8d0 000007fe`e6d49fd1 Qt5Guid!QFontDatabase::findFont(struct QFontDef * request = 0x00000000`0029eba0, int script = 2)+0x2e4 [c:\users\qt\work\qt\qtbase\src\gui\text\qfontdatabase.cpp @ 2686] 00000000`0029eb60 000007fe`e6d0be28 Qt5Guid!QFontDatabase::load(class QFontPrivate * d = 0x00000000`040a3960, int script = 2)+0x3c1 [c:\users\qt\work\qt\qtbase\src\gui\text\qfontdatabase.cpp @ 2803] 00000000`0029ec60 000007fe`e6d0ae88 Qt5Guid!QFontPrivate::engineForScript(int script = 2)+0xf8 [c:\users\qt\work\qt\qtbase\src\gui\text\qfont.cpp @ 218] 00000000`0029ecc0 000007fe`e8961328 Qt5Guid!QFontInfo::family(void)+0x28 [c:\users\qt\work\qt\qtbase\src\gui\text\qfont.cpp @ 2456] 00000000`0029ed00 000007fe`e8962424 qtquickcontrols2materialstyleplugind!QQuickMaterialTheme::QQuickMaterialTheme(class QPlatformTheme * theme = 0x00000000`00000000)+0x148 [c:\users\qt\work\qt\qtquickcontrols2\src\imports\controls\material\qquickmaterialtheme.cpp @ 50] 00000000`0029ee20 000007fe`f62e30f6 qtquickcontrols2materialstyleplugind!QtQuickControls2MaterialStylePlugin::createTheme(void)+0x24 [c:\users\qt\work\qt\qtquickcontrols2\src\imports\controls\material\qtquickcontrols2materialstyleplugin.cpp @ 115] 00000000`0029ee60 000007fe`e8961d40 Qt5QuickControls2d!QQuickStylePlugin::initializeEngine(class QQmlEngine * engine = 0x00000000`0029f590, char * uri = 0x00000000`040a35b8 "QtQuick.Controls.Material")+0xf6 [c:\users\qt\work\qt\qtquickcontrols2\src\quickcontrols2\qquickstyleplugin.cpp @ 70] 00000000`0029eec0 00000000`65d9ce00 qtquickcontrols2materialstyleplugind!QtQuickControls2MaterialStylePlugin::initializeEngine(class QQmlEngine * engine = 0x00000000`0029f590, char * uri = 0x00000000`040a35b8 "QtQuick.Controls.Material")+0x40 [c:\users\qt\work\qt\qtquickcontrols2\src\imports\controls\material\qtquickcontrols2materialstyleplugin.cpp @ 89] 00000000`0029f010 00000000`65db3737 Qt5Qmld!QQmlTypeLoaderThread::initializeEngineMain(class QQmlExtensionInterface * iface = 0x00000000`040a00e0, char * uri = 0x00000000`040a35b8 "QtQuick.Controls.Material")+0xa0 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 916] 00000000`0029f060 00000000`65e61fb2 Qt5Qmld!`QQmlThread::callMethodInMain<QQmlExtensionInterface * __ptr64,char const * __ptr64,QQmlExtensionInterface * __ptr64,char const * __ptr64,QQmlTypeLoaderThread>'::`2'::I::call(class QQmlThread * thread = 0x00000000`00356790)+0x37 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\ftw\qqmlthread_p.h @ 224] 00000000`0029f0a0 00000000`65da6865 Qt5Qmld!QQmlThread::internalCallMethodInThread(struct QQmlThread::Message * message = 0x00000000`01ca50f0)+0x162 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\ftw\qqmlthread.cpp @ 322] 1 Id: 24f8.201c Suspend: 1 Teb: 000007ff`fffdc000 Unfrozen "QQmlThread" Child-SP RetAddr Call Site 00000000`0253aeb8 000007fe`fd5f10dc ntdll!NtWaitForSingleObject+0xa 00000000`0253aec0 00000000`665d372e KERNELBASE!WaitForSingleObjectEx+0x9c 00000000`0253af60 00000000`665d3307 Qt5Cored!QWaitConditionPrivate::wait(class QWaitConditionEvent * wce = 0x00000000`04072c90, unsigned long time = 0xffffffff)+0x2e [c:\users\qt\work\qt\qtbase\src\corelib\thread\qwaitcondition_win.cpp @ 118] 00000000`0253afa0 00000000`65e635fa Qt5Cored!QWaitCondition::wait(class QMutex * mutex = 0x00000000`0034fd00, unsigned long time = 0xffffffff)+0x97 [c:\users\qt\work\qt\qtbase\src\corelib\thread\qwaitcondition_win.cpp @ 179] 00000000`0253b000 00000000`65e6221f Qt5Qmld!QQmlThreadPrivate::wait(void)+0x2a [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\ftw\qqmlthread.cpp @ 62] 00000000`0253b030 00000000`65da67ef Qt5Qmld!QQmlThread::internalCallMethodInMain(struct QQmlThread::Message * message = 0x00000000`040a3650)+0x18f [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\ftw\qqmlthread.cpp @ 359] 00000000`0253b080 00000000`65d9cb1e Qt5Qmld!QQmlThread::callMethodInMain<QQmlExtensionInterface * __ptr64,char const * __ptr64,QQmlExtensionInterface * __ptr64,char const * __ptr64,QQmlTypeLoaderThread>(<function> * Member = 0x00000000`6592115c, class QQmlExtensionInterface ** arg = 0x00000000`0253b0f8, char ** arg2 = 0x00000000`0253b100)+0x5f [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\ftw\qqmlthread_p.h @ 227] 00000000`0253b0c0 00000000`65d93b7e Qt5Qmld!QQmlTypeLoaderThread::initializeEngine(class QQmlExtensionInterface * iface = 0x00000000`040a00e0, char * uri = 0x00000000`040a35b8 "QtQuick.Controls.Material")+0x2e [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 861] 00000000`0253b0f0 00000000`65e03e38 Qt5Qmld!QQmlTypeLoader::initializeEngine(class QQmlExtensionInterface * iface = 0x00000000`040a00e0, char * uri = 0x00000000`040a35b8 "QtQuick.Controls.Material")+0xae [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 1239] 00000000`0253b140 00000000`65e09df7 Qt5Qmld!QQmlImportDatabase::importDynamicPlugin(class QString * filePath = 0x00000000`0253b368, class QString * uri = 0x00000000`0253b870, class QString * typeNamespace = 0x00000000`0253b328, int vmaj = 2, class QList<QQmlError> * errors = 0x00000000`0253ba98)+0x668 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmlimport.cpp @ 2104] 00000000`0253b2c0 00000000`65e06e23 Qt5Qmld!QQmlImportsPrivate::importExtension(class QString * qmldirFilePath = 0x00000000`0253b6a8, class QString * uri = 0x00000000`0253b870, int vmaj = 2, int vmin = 1, class QQmlImportDatabase * database = 0x00000000`00356a80, class QQmlTypeLoaderQmldirContent * qmldir = 0x00000000`0407bd60, class QList<QQmlError> * errors = 0x00000000`0253ba98)+0x507 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmlimport.cpp @ 1073] 00000000`0253b610 00000000`65e02560 Qt5Qmld!QQmlImportsPrivate::addLibraryImport(class QString * uri = 0x00000000`0253b870, class QString * prefix = 0x00000000`0253b868, int vmaj = 2, int vmin = 1, class QString * qmldirIdentifier = 0x00000000`0253b860, class QString * qmldirUrl = 0x00000000`0253b858, bool incomplete = false, class QQmlImportDatabase * database = 0x00000000`00356a80, class QList<QQmlError> * errors = 0x00000000`0253ba98)+0x273 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmlimport.cpp @ 1402] 00000000`0253b730 00000000`65d9055e Qt5Qmld!QQmlImports::addLibraryImport(class QQmlImportDatabase * importDb = 0x00000000`00356a80, class QString * uri = 0x00000000`0253b870, class QString * prefix = 0x00000000`0253b868, int vmaj = 2, int vmin = 1, class QString * qmldirIdentifier = 0x00000000`0253b860, class QString * qmldirUrl = 0x00000000`0253b858, bool incomplete = false, class QList<QQmlError> * errors = 0x00000000`0253ba98)+0x280 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmlimport.cpp @ 1628] 00000000`0253b7f0 00000000`65d97f4c Qt5Qmld!QQmlTypeLoader::Blob::addImport(struct QV4::CompiledData::Import * import = 0x00000000`01cc9380, class QList<QQmlError> * errors = 0x00000000`0253ba98)+0x4ee [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 1403] 00000000`0253ba60 00000000`65d966a3 Qt5Qmld!QQmlTypeData::continueLoadFromIR(void)+0x47c [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 2481] 00000000`0253bbc0 00000000`65d9489a Qt5Qmld!QQmlTypeData::dataReceived(class QQmlDataBlob::SourceCodeData * data = 0x00000000`0253bc88)+0xb3 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 2399] 00000000`0253bc00 00000000`65d947f1 Qt5Qmld!QQmlTypeLoader::setData(class QQmlDataBlob * blob = 0x00000000`01c9aa70, class QQmlDataBlob::SourceCodeData * d = 0x00000000`0253bc88)+0x8a [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 1271] 00000000`0253bc50 00000000`65d93ff7 Qt5Qmld!QQmlTypeLoader::setData(class QQmlDataBlob * blob = 0x00000000`01c9aa70, class QString * fileName = 0x00000000`0253bcf0)+0x81 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 1260] 00000000`0253bcb0 00000000`65d9cc11 Qt5Qmld!QQmlTypeLoader::loadThread(class QQmlDataBlob * blob = 0x00000000`01c9aa70)+0x297 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 1136] 00000000`0253bde0 00000000`65db377e Qt5Qmld!QQmlTypeLoaderThread::loadThread(class QQmlDataBlob * b = 0x00000000`01c9aa70)+0x21 [c:\users\qt\work\qt\qtdeclarative\src\qml\qml\qqmltypeloader.cpp @ 876] 2 Id: 24f8.16d0 Suspend: 1 Teb: 000007ff`fffda000 Unfrozen "QQmlDebugServerThread" Child-SP RetAddr Call Site 00000000`032ac128 000007fe`fd5f1430 ntdll!NtWaitForMultipleObjects+0xa 00000000`032ac130 00000000`77492ce3 KERNELBASE!GetCurrentProcess+0x40 00000000`032ac230 00000000`7738bc3d kernel32!WaitForMultipleObjectsEx+0xb3 00000000`032ac2c0 00000000`7738905a USER32!PeekMessageW+0x1cd 00000000`032ac360 00000000`66a44761 USER32!MsgWaitForMultipleObjectsEx+0x2a 00000000`032ac3a0 00000000`66982bc8 Qt5Cored!QEventDispatcherWin32::processEvents(class QFlags<enum QEventLoop::ProcessEventsFlag> flags = class QFlags<enum QEventLoop::ProcessEventsFlag>)+0x7b1 [c:\users\qt\work\qt\qtbase\src\corelib\kernel\qeventdispatcher_win.cpp @ 648] 00000000`032af750 00000000`66982e0e Qt5Cored!QEventLoop::processEvents(class QFlags<enum QEventLoop::ProcessEventsFlag> flags = class QFlags<enum QEventLoop::ProcessEventsFlag>)+0x68 [c:\users\qt\work\qt\qtbase\src\corelib\kernel\qeventloop.cpp @ 135] 00000000`032af790 00000000`665bfcaf Qt5Cored!QEventLoop::exec(class QFlags<enum QEventLoop::ProcessEventsFlag> flags = class QFlags<enum QEventLoop::ProcessEventsFlag>)+0x18e [c:\users\qt\work\qt\qtbase\src\corelib\kernel\qeventloop.cpp @ 212] 00000000`032af840 000007fe`f60f4cc2 Qt5Cored!QThread::exec(void)+0xbf [c:\users\qt\work\qt\qtbase\src\corelib\thread\qthread.cpp @ 515] 00000000`032af8b0 00000000`665cc50d qmldbg_serverd!QQmlDebugServerThread::run(void)+0x2a2 [c:\users\qt\work\qt\qtdeclarative\src\plugins\qmltooling\qmldbg_server\qqmldebugserver.cpp @ 259] 00000000`032af970 00000000`7748652d Qt5Cored!QThreadPrivate::start(void * arg = 0x00000000`003f0e18)+0x19d [c:\users\qt\work\qt\qtbase\src\corelib\thread\qthread_win.cpp @ 380] 00000000`032afa00 00000000`775bc541 kernel32!BaseThreadInitThunk+0xd 00000000`032afa30 00000000`00000000 ntdll!RtlUserThreadStart+0x21

@hskoglund said in Crushes after deploying!:

Hi, googling finds many with the same problem, for example here
Just guessing, but perhaps you could try some of the suggestions in there...

Thanks for the link.
It seems this issue doesn't even solved in Stack Overflow :(

Any way, I did some of the suggestions mentioned in it.

Installed all redistributable package of x86 (cuz I built my app using Qt mingw53_32) for 2012 - 2013 - 2015 - 2017 (I tested my app after each vcredist) Installed all redistributable package of x64 for 2012 - 2013 - 2015 - 2017 (I tested my app after each vcredist)

Nothing changed still see my app crashes without any logical reason!

Now I'm very sad because I can run my app only if I installed Qt on my machine which is impractical solution for deploying my app.

Ok. I have found the issue.

Since QT5_WRAP_UI macro is delivered as part of Qt5Widget packacge it is necessery to make a call to find_package (Qt5Widget) before issuing QT5_WRAP_UI call.

Ehh :D

yes, specify 32 and 64 for msvc2015
i was able to ignore the warnings
the kits i picked worked