Hi, with QT_OPENGL=software I even have 8 opengl32sw threads, but an idle Qt Creator uses less than overall 1% CPU. The issue you have seems to be related to your graphics stack. Can you provide some details on your graphics stack (drivers, versions) preferably as a bug report (bugreports.qt.io)?
Kind Regards, Thomas Hartmann -----Ursprüngliche Nachricht----- Von: Tilman Skobowsky [mailto:skobow...@caos-gmbh.de] Gesendet: Thursday, April 13, 2017 11:41 AM An: Thomas Hartmann <thomas.hartm...@qt.io> Betreff: Re: [Qt-creator] QtCreator 4.3b1 background thread running? Hi, I was too fast answering the first hint. Now I tried again setting QT_OPENGL and, voilà, the problem is almost gone. Instead of the one thread using half a CPU core I do have 4 opengl32sw threads which alltogether permanently do something. At least the Cycles Delta value for each of the 4 thread ranges from 5M to 10M. Tilman Am 13.04.2017 um 11:34 schrieb Thomas Hartmann: > Hi, > > -noload Welcome is not required anymore, since the Welcome Page was > reimplemented using widgets. > An alternative to avoid OpenGL issues on Windows is "set QT_OPENGL=software". > I cannot reproduce the issue on my Windows 10 setup. > > Kind Regards, > Thomas Hartmann > > -----Ursprüngliche Nachricht----- > Von: Qt-creator > [mailto:qt-creator-bounces+thomas.hartmann=qt...@qt-project.org] Im > Auftrag von Henry Skoglund > Gesendet: Thursday, April 13, 2017 11:28 AM > An: qt-creator@qt-project.org; skobow...@caos-gmbh.de > Betreff: Re: [Qt-creator] QtCreator 4.3b1 background thread running? > > Hi, you could try starting Qt Creator from a CMD window (universal solution > #1 for opengl problems) to see if the CPU consumption subsides: > > qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler > > Rgrds Henry > > On 2017-04-13 11:20, Tilman Skobowsky wrote: >> Hi, >> >> I just downloaded Qt-Creator 4.3.0 b1 for some testing. >> What immediately struck me was the ongoing action in one thread that >> consumes about half a CPU core's performance. >> The stacktrace (taken with ProcessExplorer) is >> >> 0 ntdll.dll!ZwRequestWaitReplyPort+0xa >> 1 dwmapi.dll!DwmSetWindowAttribute+0x1cc >> 2 dwmapi.dll!DwmSetWindowAttribute+0x3d0 >> 3 dwmapi.dll!Ordinal132+0x97a >> 4 dwmapi.dll!DwmSetWindowAttribute+0x2cc >> 5 dwmapi.dll!DwmFlush+0x92 >> 6 ig75icd64.dll!DrvValidateVersion+0x139a >> 7 kernel32.dll!BaseThreadInitThunk+0xd >> 8 ntdll.dll!RtlUserThreadStart+0x21 >> >> Checking on the web I found an entry on the Team Speak forum where >> they observed the same issue but with a different Qt-based software. >> As described there, I can kill the thread without noticing a real >> problem when using Qt-Creator. >> >> I double checked this with both 32bit and 64bit. The problem occurrs >> in both versions. >> My machine runs Win7 >> >> Any ideas? >> >> TIA >> Tilman >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator >> > > _______________________________________________ > Qt-creator mailing list > Qt-creator@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
