Qt Creator 4.9.1 does not start on Windows 10

chrizbee

Hey there,

I've been able to use Qt Creator for quite a while now. Today I've tried to open Qt Creator a second time (2 at once) which resulted in a Bluescreen.
After restarting I'm not able to start Qt Creator anymore.

Tested with reinstalling (online and offline installer) with Qt 5.13.0 and Qt Creator 4.9.1.
Starting as admin does work, but is not the workaround I'm after.
Starting with "qtcreator.exe -noload all -load Core" opens Qt Creator with a very stripped-down version.

Windows Event Viewer log:

- System 
  - Provider 
   [ Name]  Application Error 
  - EventID 1000 
   [ Qualifiers]  0 
   Level 2 
   Task 100 
   Keywords 0x80000000000000 
  - TimeCreated 
   [ SystemTime]  2019-07-24T11:54:30.071843800Z 
   EventRecordID 3874 
   Channel Application 
   Computer DESKTOP-KP2VGVR 
   Security
- EventData
   qtcreator.exe 
   4.9.1.0 
   5ceb0248 
   Qt5Core.dll 
   5.12.3.0 
   5cac76e7 
   c0000005 
   0018c807 
   1594 
   01d542168c7e0887 
   C:\Qt\Qt5.13.0\Tools\QtCreator\bin\qtcreator.exe 
   C:\Qt\Qt5.13.0\Tools\QtCreator\bin\Qt5Core.dll 
   810bfe66-645b-4990-ae17-bcf0fdf80d67

GDB log:

Starting program: C:\Qt\Qt5.13.0\Tools\QtCreator\bin\qtcreator.exe
[New Thread 3196.0xeac]
[New Thread 3196.0xeb0]
[New Thread 3196.0x1b70]
[New Thread 3196.0x630]
[New Thread 3196.0x23c4]
[New Thread 3196.0x2f08]
[Thread 3196.0x2f08 exited with code 0]
[New Thread 3196.0x2f58]
[New Thread 3196.0x13f0]
[New Thread 3196.0x2da8]
[New Thread 3196.0x2dac]
[New Thread 3196.0x2dc4]
warning: SOFT ASSERT: "m_file.open()" in file C:\Users\qt\work\build\qt-creator\src\plugins\perfprofiler\perfprofilertracemanager.cpp, line 77
[New Thread 3196.0x2e24]

Thread 1 received signal SIGSEGV, Segmentation fault.
0x6422c807 in Qt5Core!?activate@QMetaObject@@SAXPAVQObject@@HHPAPAX@Z ()
   from C:\Qt\Qt5.13.0\Tools\QtCreator\bin\Qt5Core.dll

Feel free to ask for the information you need. I hope this can be resolved soon.
Thank you in advance!

aha_1980

@chrizbee Can you try to start Creator with the parameter -tcs (temporary clean settings)?

From your description, it sounds like the settings are corrupted and Creator therefore does not start.

chrizbee

@aha_1980 Thank you for your suggestion.
I've tried that already. Same result. Works as admin and does not work as normal user.

chrizbee

Small update:
When I start Qt Creator it does not open at all, but it does create the following folders on my main drive:

clangbackend-sZLsZL
clang-uiheader-sZLsZL

Those folders seem to have a different letter combination everytime I start Qt Creator.
Any clues on that?

clangfolders

jsulm

@chrizbee Probably temporary folders, not deleted because QtCreator crashes.

chrizbee

@jsulm But the GDB log should give a hint as to where it crashes, right? Any ideas on that?

jsulm

@chrizbee Try to start QtCreator from a terminal with "-noload all" parameter. It disables all plugins. If it works then you can try to disable one plug-in after another to see which one causes troubles, like "-noload Welcome".

chrizbee

@jsulm
Following works (did I miss any plugins?):

qtcreator -noload all -load Core -load Debugger -load Git -load ProjectExplorer -load QmlDesigner -load Welcome

While this still doesn't:

qtcreator

EDIT:
Okay, I've tested all plugins that are listed in "--help" (perfprofiler plugin is not?)

What works:

qtcreator -noload Debugger
qtcreator -noload ProjectExplorer

What does not work:

qtcreator -noload Git
qtcreator -noload QmlDesigner
qtcreator -noload Welcome

jsulm

@chrizbee From the GDB log it is perfprofiler plug-in

chrizbee

Another Update:
I've just completely uninstalled Qt 5.13.0 and installed Qt 5.12.4 using the offline installer.
Same result (as expected, since both are using Qt Creator 4.9.1).

hskoglund

Hi, just guessing but maybe your temp environment variables have a bad setting, to check, open a CMD window and type:

echo %TEMP%
echo %TMP%

chrizbee

@hskoglund
Should be fine.

λ echo %TEMP%
C:\Users\chrba\AppData\Local\Temp

λ echo %TMP%
C:\Users\chrba\AppData\Local\Temp

But I'm guessing too, that there's some "bad settings" stored somewhere which I didn't delete yet.
Because it was working before...

hskoglund

Also, what you can try: create another, new user. Switch to that user and start Qt Creator.

chrizbee

Qt 5.9.8 offline installer with Qt Creator 4.8.2 works flawlessly.

chrizbee

@hskoglund I can start Qt Creator from another user without any problems.
But what are the differences related to Qt Creator?
Environment variables? Registry entries?
Why would it work for the new user and not for my default one?

jsulm

@chrizbee said in Qt Creator 4.9.1 does not start on Windows 10:

Environment variables? Registry entries?
Why would it work for the new user and not for my default one?

Because there is probably something broken (like environment variables, registry, entries in the file system,...)

aha_1980

@jsulm And given it works with 4.8, probably some new setting introduced in 4.9...

chrizbee

@jsulm said in Qt Creator 4.9.1 does not start on Windows 10:

@chrizbee From the GDB log it is perfprofiler plug-in

Perfprofiler is not the problem ("only" soft assert). I disabled the plugin and retried with the same result (GDB has no soft assert anymore, but the SIGSEGV is still there).

@aha_1980 said in Qt Creator 4.9.1 does not start on Windows 10:

@jsulm And given it works with 4.8, probably some new setting introduced in 4.9...

Now here comes the strange part:
I've installed Qt 5.13.0 and tried the following standalone Qt Creator installers:
4.9.2 / 4.9.1 / 4.9.0 / 4.8.2 (both 32 and 64 bit) --> Neither of those worked.

So I've figured that the combination is where the problem is coming from.
Given this GDB log:

Thread 1 received signal SIGSEGV, Segmentation fault.
0x6422c807 in Qt5Core!?activate@QMetaObject@@SAXPAVQObject@@HHPAPAX@Z ()
   from C:\Qt\Qt5.13.0\Tools\QtCreator\bin\Qt5Core.dll

I still do not have a solution to my problem, just a few workarounds which are quite nasty...

aha_1980

@chrizbee said in Qt Creator 4.9.1 does not start on Windows 10:

Given this GDB log:

Can you go upwards the stack trace and see where this crash originates from?

Anyway, if it works in a fresh user account I'd probably rename my account, create a new one and copy over all the things I need. It's a bit of work, but still faster than reinstalling the whole system.

Just my 2ct.

chrizbee

@aha_1980 said in Qt Creator 4.9.1 does not start on Windows 10:

Anyway, if it works in a fresh user account I'd probably rename my account, create a new one and copy over all the things I need. It's a bit of work, but still faster than reinstalling the whole system.

I actually ended up reinstalling the whole system. Still, this should not happen...