QtCreator crashed and now will not start due to segfault

TMcSquared · 8 Oct 2018, 05:41

Hello everyone, I'm having a bit of a struggle liking Qt-Creator ever since it crashed while I was working on it. I've re-installed Qt several times, but nothing is changing. Are there some hidden config files I should be removing? Does anyone else have this problem?

mrjj · wrote on 9 Aug 2018, 13:09

Hi and welcome to the forums
What version of Creator and what Os ?

I have not have it crash for a long time (years)
so most likely something else wrong.

What are you doing when it crashes ?

Also could you try upgrading your gfx driver ?

TMcSquared · 9 Aug 2018, 15:06

Qt-Creator 4.7.0 on Windows 10
I think I overloaded it clicking on settings(not exactly sure though)
I don't think the gfx driver's an issue because it was running fine yesterday, and I haven't had anything change on my machine.

mrjj · wrote on 9 Aug 2018, 15:06

@TMcSquared

Ok, if it was working yesterday. then cant be the gfx is no windows update
or anything.

Can you still reproduce it ?

TMcSquared · 9 Aug 2018, 15:10

Yes, Qt-Creator just won't open at all, even after I re-install the entire thing.

mrjj · 8 Sept 2018, 15:10

@TMcSquared

Ok, that is odd.

there is
C:\Users\username\AppData\Local\QtProject
C:\Users\username\AppData\Roaming\QtProject
which can be left over even if reinstall.

It should be pretty safe to delete, but Creator will forget anything then.

TMcSquared · 9 Aug 2018, 15:20

I've deleted those already between installs

mrjj · 8 Sept 2018, 15:22

@TMcSquared
and it still crashes ? wow. thats new.
Do you have sessions enabled ?
also , have you tried starting it from a shell (cmd)
to see if anything is written ?

also when starting in cmd.
try adding
-noload Welcome

TMcSquared · 9 Aug 2018, 15:51

I get a segmentation fault when I run it from the cmdline both without and with arguments.

JonB · wrote on 9 Aug 2018, 15:51

@TMcSquared
There's, oohh, a 1% chance that if you try running Qt Creator from within a debugger like Visual Studio (if you have that...), when it faults you'll get enough information from the stack trace to hazard a guess as to where it's going wrong...

TMcSquared · 9 Aug 2018, 16:54

I just debugged it and got this: Exception thrown at 0x670E5DA7 (Qt5Core.dll) in qtcreator.exe: 0xC0000005: Access violation reading location 0x7E5B8721.

aha_1980 · wrote on 9 Aug 2018, 16:54

@TMcSquared

Is it possible that the wrong Qt DLLs are loaded? Have you changed the PATH environment variable, for example?

TMcSquared · 9 Aug 2018, 16:56

Hmm I'll try adding it to the PATH xD

EDIT: that didn't work

aha_1980 · wrote on 9 Aug 2018, 16:56

@TMcSquared

No, that's not what I meant! I meant, have you done before? Or have you installed some program that did?

mranger90 · wrote on 9 Aug 2018, 17:00

Take a look at qt.conf in the creator/bin directory. If it's corrupted then plugins wont load.

TMcSquared · wrote on 9 Aug 2018, 17:12

It's not corrupted because it's a clean install

mranger90 · wrote on 9 Aug 2018, 19:08

The try wiping out the creator files under AppData\Roaming\Qtproject

TMcSquared · 9 Aug 2018, 19:28

already did that.

mrjj · wrote on 9 Aug 2018, 19:28

@TMcSquared
Best guess is that it gets wrong QtDLLs maybe via
path.

TMcSquared · 9 Aug 2018, 20:32

My PATH variable has zero Qt paths in it. even after a clean install.