QtCreator crashed and now will not start due to segfault
-
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.Ok, if it was working yesterday. then cant be the gfx is no windows update
or anything.Can you still reproduce it ?
-
wrote on 9 Aug 2018, 15:07 last edited by
Yes, Qt-Creator just won't open at all, even after I re-install the entire thing.
-
Yes, Qt-Creator just won't open at all, even after I re-install the entire thing.
Lifetime Qt Championwrote on 9 Aug 2018, 15:10 last edited by mrjj 8 Sept 2018, 15:10Ok, 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.
-
wrote on 9 Aug 2018, 15:19 last edited by
I've deleted those already between installs
-
I've deleted those already between installs
Lifetime Qt Championwrote on 9 Aug 2018, 15:20 last edited by 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 -
wrote on 9 Aug 2018, 15:41 last edited by
I get a segmentation fault when I run it from the cmdline both without and with arguments.
-
I get a segmentation fault when I run it from the cmdline both without and with arguments.
wrote on 9 Aug 2018, 15:51 last edited by@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... -
wrote on 9 Aug 2018, 16:20 last edited by
I just debugged it and got this: Exception thrown at 0x670E5DA7 (Qt5Core.dll) in qtcreator.exe: 0xC0000005: Access violation reading location 0x7E5B8721.
-
I just debugged it and got this: Exception thrown at 0x670E5DA7 (Qt5Core.dll) in qtcreator.exe: 0xC0000005: Access violation reading location 0x7E5B8721.
Is it possible that the wrong Qt DLLs are loaded? Have you changed the PATH environment variable, for example?
-
wrote on 9 Aug 2018, 16:55 last edited by TMcSquared 8 Sept 2018, 16:59
Hmm I'll try adding it to the PATH xD
EDIT: that didn't work
-
Hmm I'll try adding it to the PATH xD
EDIT: that didn't work
No, that's not what I meant! I meant, have you done before? Or have you installed some program that did?
-
wrote on 9 Aug 2018, 17:00 last edited by
Take a look at qt.conf in the creator/bin directory. If it's corrupted then plugins wont load.
-
wrote on 9 Aug 2018, 17:12 last edited by
It's not corrupted because it's a clean install
-
wrote on 9 Aug 2018, 19:08 last edited by
The try wiping out the creator files under AppData\Roaming\Qtproject
-
wrote on 9 Aug 2018, 19:20 last edited by
already did that.
-
already did that.
@TMcSquared
Best guess is that it gets wrong QtDLLs maybe via
path. -
wrote on 9 Aug 2018, 20:30 last edited by
My PATH variable has zero Qt paths in it. even after a clean install.
-
My PATH variable has zero Qt paths in it. even after a clean install.
@TMcSquared
I have no idea then.
last test
can you start with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler
from shell and see if still crash ? -
@TMcSquared
I have no idea then.
last test
can you start with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler
from shell and see if still crash ?wrote on 9 Aug 2018, 20:51 last edited by:O It opened with
qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler -
Hi,
Then it sounds like a graphic driver issue then. Are you sure there wasn't any modification in that regard on your machine ?
13/35