QT Creator starts very slow
-
Many people complained about that, and even though plenty assurances in the quality of recent iterations of Creator were made, fact is it is much, much slower than it used to be in this time last year. Disabling plugins doesn't help either. I guess that is just the way things are going to be, but hey, on the bright side it is still a little faster than VS2012. You can always get a faster PC, but even on a powerful high end workstation it is laggy, I have a cutting edge rig with loads of ram, best desktop CPU money can buy and one of the fastest SDDs on the market and it still hangs for a few seconds. On my laptop it is really annoying due to the lower specs. But it is not like I can switch back to the old Creator, it lacks in support of important features.
The easiest solution to deal with something that starts slowly... is to not stop it. Then you don't have to wait for it to start all the time. It will drain some ram, but ram is cheap and plentiful these days, while time you cannot buy.
-
@double_ter: Not really. I installed the latest version of the SDK at the time, as they recommended, but it didn't work with the latest version of Qt Creator. I had to install them separately and rejig configuration settings to get Qt to find it, and I never got debugging working again.
However, with the mis-matched versions eventually half-working, it did start immediately, maybe because some things just failed immediately instead of waiting. Since debugging didn't work and other features were half-working, along with lots of crashing, I just gave up on Qt Creator. It's not worth the pain. VS2012 is mediocre, but it at least has basic functionality.
@utcenter: It has nothing to do with computer performance, because the program is not doing anything. Qt Creator sits there not accessing the harddrive or network and not using the CPU for minutes, presumably waiting for network timeouts.
There's no window open yet, so it just looks like Qt Creator doesn't work at all, then suddenly several minutes later, it pops up after I've moved on with life and resigned myself to that Qt Creator simply won't run on my platform. Then I go online to search for other people with the same problem, and find that there's nothing but denials from the dev team even though it's been reported repeatedly for years, and it's reproducible every single time I run it and every single time I've installed it, on multiple computers and multiple versions of Qt Creator.
-
utcenter: What exactly is slower than it used to be?
double_ter: That behavior suggest that creator is running into some issue, waiting for something to time out. Is there any chance that you can find out what that might be (e.g. by running a process monitor on it)? We had an issue a while back where having '' in the PATH (e.g. PATH=C:\windows\system32;;C:\something) caused creator to wait for network drives that were never going to appear, but that should be fixed.
-
Neil Dickson - for me it does, as I said on my desktop it is just a few seconds, it is significantly more on my laptop. This goes for the actual startup of Creator.
Then there is the project loading hiccup, which could easily be solved by making parsing asynchronous.
I was under the impression Creator also tries to load some stuff of the internet, blog entries IIRC, but that went away when I disabled the welcome screen.
Tobias Hunger - it might be just the extra features, pretty much every application gets a little slower to startup with iterations. I admit I might be a little spoiled in this regard, since I find waiting extremely annoying when working on old and slow machines.
-
I've updated to Qt 5.1 and Qt Creator 2.8 and got the same issue.
[quote author="Tobias Hunger" date="1344852817"]
I know I am asking much, but could you please try the most recent Qt Creator (2.5.2) again, running it from the command line using the "-profile" option? That gives a somewhat detailed list of times spent on loading and initializing the plugins (incl. the different phases of the initialization). That could be a big help in finding out what is going wrong.[/quote]I did it. Results:
@
TaskList 2ms ( 0.00% )
CodePaster 3ms ( 0.00% )
ResourceEditor 3ms ( 0.00% )
ClassView 4ms ( 0.00% )
PythonEditor 6ms ( 0.01% )
RemoteLinux 6ms ( 0.01% )
QmlProjectManager 6ms ( 0.01% )
Qt4ProjectManager 7ms ( 0.01% )
Perforce 8ms ( 0.01% )
Subversion 8ms ( 0.01% )
QmlProfiler 8ms ( 0.01% )
Bookmarks 9ms ( 0.01% )
ClearCase 10ms ( 0.01% )
Mercurial 11ms ( 0.01% )
BinEditor 13ms ( 0.01% )
DiffEditor 14ms ( 0.01% )
Bazaar 16ms ( 0.01% )
Macros 16ms ( 0.01% )
FakeVim 17ms ( 0.01% )
Locator 17ms ( 0.01% )
CVS 17ms ( 0.01% )
Valgrind 21ms ( 0.02% )
ImageViewer 21ms ( 0.02% )
Qnx 24ms ( 0.02% )
GenericProjectManager 24ms ( 0.02% )
CppEditor 26ms ( 0.02% )
CMakeProjectManager 27ms ( 0.02% )
GLSLEditor 27ms ( 0.02% )
VcsBase 30ms ( 0.03% )
Git 33ms ( 0.03% )
Android 35ms ( 0.03% )
TextEditor 39ms ( 0.03% )
QmlJSEditor 50ms ( 0.04% )
QmlJSTools 56ms ( 0.05% )
QmlDesigner 63ms ( 0.05% )
Designer 71ms ( 0.06% )
CppTools 71ms ( 0.06% )
QtSupport 84ms ( 0.07% )
Find 89ms ( 0.07% )
Debugger 97ms ( 0.08% )
Help 196ms ( 0.16% )
AnalyzerBase 461ms ( 0.39% )
Welcome 2817ms ( 2.37% )
Core 3315ms ( 2.78% )
ProjectExplorer 111193ms ( 93.38% )
Total: 119071ms
@For be sure I renamed qt settings (QtProject.conf and QtProject dir in ~/.config). It didn't help. What's more incomprehensible is that qt creator doesn't load project at start and I cannot understand why ProjectExplorer loading takes more than 100 ms. If it loads, OK, some projects are huge, but it is not.
What can I make else to help developers fix that issue?
UPD1:
I rebooted after installation and now all works normally:
@
ClassView 0ms ( 0.00% )
BinEditor 1ms ( 0.01% )
ImageViewer 2ms ( 0.02% )
ResourceEditor 2ms ( 0.02% )
Android 2ms ( 0.02% )
DiffEditor 2ms ( 0.02% )
FakeVim 3ms ( 0.04% )
Qnx 3ms ( 0.04% )
Bookmarks 3ms ( 0.04% )
CodePaster 3ms ( 0.04% )
GenericProjectManager 4ms ( 0.05% )
Macros 4ms ( 0.05% )
Valgrind 4ms ( 0.05% )
RemoteLinux 4ms ( 0.05% )
VcsBase 4ms ( 0.05% )
QmlProjectManager 4ms ( 0.05% )
Mercurial 5ms ( 0.06% )
Bazaar 5ms ( 0.06% )
TaskList 5ms ( 0.06% )
ClearCase 6ms ( 0.07% )
PythonEditor 6ms ( 0.07% )
QmlProfiler 7ms ( 0.09% )
Designer 7ms ( 0.09% )
Perforce 7ms ( 0.09% )
CVS 8ms ( 0.10% )
GLSLEditor 8ms ( 0.10% )
Qt4ProjectManager 8ms ( 0.10% )
Subversion 9ms ( 0.11% )
CppEditor 10ms ( 0.12% )
CMakeProjectManager 10ms ( 0.12% )
Git 11ms ( 0.14% )
Locator 13ms ( 0.16% )
CppTools 15ms ( 0.19% )
TextEditor 19ms ( 0.24% )
QmlJSEditor 29ms ( 0.36% )
Find 50ms ( 0.62% )
Debugger 54ms ( 0.67% )
QmlDesigner 56ms ( 0.69% )
QmlJSTools 58ms ( 0.72% )
QtSupport 70ms ( 0.87% )
AnalyzerBase 128ms ( 1.59% )
Help 206ms ( 2.55% )
ProjectExplorer 1094ms ( 13.55% )
Welcome 2850ms ( 35.31% )
Core 3273ms ( 40.55% )
Total: 8072ms
@I cannot understand the reason to work badly until reboot, but if there are some difficulties it's better to warn user to reboot (what is of course not good, since Qt is not Windows, isn't it? :) ).
-
[quote author="Tobias Hunger" date="1344758912"]Hey, I do respond to the few reports I see about startup issues. I just can't do much without some hint as to what actually is going wrong. And even if I had an idea I can not verify that the issue is fixed without a way to reproduce. You are a developer, you know the drill.
Please try to reproduce this with a more recent version of Qt Creator. Some startup issues were fixed since 2.3.0. The updated Qt that comes with a new Qt Creator might also help: There was one issue where Qt was blocking in an call that was supposed to be async when trying to resolve proxy settings on windows. Maybe making sure those settings are sensible can speed up creator for you. Finally you can try to disable plugins in creator to narrow down which one causes the delay. If this is indeed network related then start with the welcome plugin: That is the only one that has network activity on startup (fetches the newsfeed). That gives some hint as to what is going wrong and if you don't need that plugin it also provides a workaround for the time being. If you previously used older Creator versions wiping the configuration can also help. That is the very last thing I'd try though as that obviously resets everything and it is unlikely that this causes the issue.
PS: That '' is caused trouble on windows only (issue is fixed in newer Qt Creator versions) and some preinstalled software from a vendor seems to put it into PATH.[/quote]
It's still there in QT4.8.3 Open Scource.
This is how the bug happens.
compile Qt for VS2010 Ultimate x64 System.
install add in.SOfar everythign works.
If you open .pro files with the Add in it's all fine,
if you use qmake.exe from the x64 command prompt from vs2010
you cannot start the Designer, Assasting and everything else in the bin folder.
Installting the hotfix VS10-KB2280741-x86 after this problem, it doesnt help either :( -
I've been having the slow-loading problem as well. Qt Designer takes on the order of minutes to load. I'm not using the latest versions of Qt software, because the latest versions were incompatible with my system. I used the latest versions that all played well together.
- Qt 5.4.0
- Windows 7
- Visual Studio 2012, Update 4
- Qt Visual Studio add-in 1.2.2
-
I've been having the slow-loading problem as well. Qt Designer takes on the order of minutes to load. I'm not using the latest versions of Qt software, because the latest versions were incompatible with my system. I used the latest versions that all played well together.
- Qt 5.4.0
- Windows 7
- Visual Studio 2012, Update 4
- Qt Visual Studio add-in 1.2.2
-
[quote author="CueTeeDuntz" date="1424377109"]I've been having the slow-loading problem as well. Qt Designer takes on the order of minutes to load. I'm not using the latest versions of Qt software, because the latest versions were incompatible with my system. I used the latest versions that all played well together.
- Qt 5.4.0
- Windows 7
- Visual Studio 2012, Update 4
- Qt Visual Studio add-in 1.2.2[/quote]Hi, and welcome to the Qt Dev Net!
Does disabling your antivirus help?
-
[quote author="CueTeeDuntz" date="1424377109"]I've been having the slow-loading problem as well. Qt Designer takes on the order of minutes to load. I'm not using the latest versions of Qt software, because the latest versions were incompatible with my system. I used the latest versions that all played well together.
- Qt 5.4.0
- Windows 7
- Visual Studio 2012, Update 4
- Qt Visual Studio add-in 1.2.2[/quote]Hi, and welcome to the Qt Dev Net!
Does disabling your antivirus help?
-
I have no antivirus software, and Windows "Defender" is disabled.
-
I have no antivirus software, and Windows "Defender" is disabled.
-
[quote author="CueTeeDuntz" date="1424460795"]I have no antivirus software, and Windows "Defender" is disabled.[/quote]Hmm... I'm not sure then, sorry.
Try opening Qt Designer through the Qt Creator IDE -- is it slow there too?
-
This post is deleted! -
The delay sure is there; I have it here on some PC's. Some are better than others. But the delays vary from 5s on one PC to 30s and upto 2 minutes on another. Even on relatively clean PC's with almost no installations, the problem is there.
We're tracking the problem currently by delving into the source code. At the start, there is a scan taking place of the Qt*.dll directory and the .exe directory (at least). Probably looking for possible plugins. One of the calls taking place is QT_FSTAT, which goes into a qfilesystemengine_win.cpp function and does something of an fstat(), namely GetFileAttributesEx().
Here, at some point, it introduces a delay of ~20 seconds almost everytime (on my Win7 machine). It's not really Qt related it seems, or perhaps it is. The call is into Win32, and we'll check it out if we can tweak some of the input parameters to get it to work. One thing I see is that the output buffer of the call is uninitialized. Perhaps Windows uses something after all from the output buffer, and now & then breaks on some garbage.
This is using Qt 5.3.0 IIRC. More tomorrow hopefully, if we can get the call to behave.
Turning Windows Defender/MSE on/off has no effect. I see the problem on at least 3 different PC's with different backgrounds, all running Windows 7 64 bits though. -
Ok, this is awkward but hopefully others will benefit from this discovery; the reason why this was slow was because there were shortcuts to the network. So we had a shortcut file pointing to this 10.1.90.121 UNC file, and that PC didn't exist in the network. So it was just a hang on this file while Windows was trying to reach the machine. Still, it had us boggled for quite a bit of time.
We might delve a bit further to see how Qt handles UNC files it encounters, because any network shortcut will be reason for possibly quite long delays. I'd rather not scan directories anyway.
-
This post is deleted! -
@rvangaal it worked for me - Thank you!!