Qt Creator 4.9.1 does not start on Windows 10

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...

aha_1980

@chrizbee I have three or more more instances of Creator open daily, so I'm pretty sure you had really bad luck...

This should never happen again.