i found what caused the issue: I accidentally also linked some other code to the application in which a static initialization of a QNetworkAccessManger happened. This also explains the different behavior between release and debug mode.
>> QEventLoop: Cannot be used without QApplication > > Says everything. > > Show your code. > > Regards, > Konstantin > > 2015-03-30 23:21 GMT+04:00 raven-worx Software <i...@raven-worx.net>: > >> Hi, >> >> i get the following print outs to the console and absolutley have no clue >> why: >> >> SHIMVIEW: ShimInfo(Complete) >> QEventLoop: Cannot be used without QApplication >> QObject::connect: Cannot connect (null)::aboutToQuit() to >> QNativeWifiEngine::closeHandle() >> >> But this only happens in RELEASE MODE! DEBUG mode works fine and these >> print outs are not showing up. >> >> I even get these print outs when my main() only returns 0, so no >> QApplication is instantiated meaning as soon as i link against Qt >> binaries. >> >> Once the application starts up i also noticed that (queued) signals >> from other threads are not delivered anymore, which most probably >> involves the QEventLoop error message somehow. But on the other hand >> events from the OS are delivered. >> >> I am using: >> QtCreator 3.3.1, MSVC2012, Qt 5.4.1 >> >> >> _______________________________________________ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development >> > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development