Qt creator ошибка 0xc0000005

Qt creator error 0xc0000005

Hello everybody,
I’m having a hard time installing Qt Creator on windows 7 x64

I’ve tried the offline installer, online installer:
qt-creator-opensource-windows-x86_64-6.0.0.exe
qt-unified-windows-x86-4.2.0-online.exe

Both give me an immediate error:
«The application was unable to start correctly (0xc0000005).
Click OK to close the application»

Any ideas what might be the issue?

@Mojofarmer QtCreator 6 is based on Qt6 which does not support Windows 7 anymore.
You will have to stay with QtCreator 5.
Or, better, upgrade to a more recent Windows version, as Windows 7 reached end of life quite some time ago already.

Thanks a lot jslum!

I’ll give Qt5 a try first, not too excited about having to upgrade my OS right now.

Downloading qt-everywhere-src-5.15.2.zip from:
https://download.qt.io/archive/qt/5.15/5.15.2/ should get me up and running just like qt-creator-opensource-windows-x86_64-6.0.0.exe would have, right?

@Mojofarmer Use the Qt online installer to install Qt and QtCreator offline installer from https://download.qt.io/official_releases/qtcreator/5.0/5.0.3/ to install QtCreator 5.

@jsulm Thanks a lot for your help jslum!

FWIW I’ve made a relevant FR asking for Win7 support in the online installer (essentially, asking to add QtCreator 5 back to the available component repos) at https://bugreports.qt.io/browse/QTBUG-100421.

Also, if anybody’s looking, a full directory of older Creator versions can be found at https://download.qt.io/official_releases/qtcreator/ (there doesn’t seem to be a direct link to past versions on the main website).

I had success with @jsulm’s suggestion; using the latest online installer (you can install the Qt5 toolchains with it still) and then separately installing Qt Creator 5 alongside it (in a different directory). It does leave the non-working Qt Creator 6 installed but it mostly doesn’t hurt anything, just takes up some extra drive space.

Источник

Qt creator error 0xc0000005

Hi all,
I’m experiencing a strange problem. A qt application I’ve made runs correctly on a windows system for some time, then it suddenly stops running (client says he didn’t do anything and that it just stopped working). Once this happens, the application cannot start anymore (tried reinstalling the app but no luck).

This is what I get from the Windows event data:

Any clues to what might be causing this problem?

@nwoki
I’ll be amazed if anyone can tell you anything from this information! ( error 0xc0000005 is «Access violation error», so memory is being accessed wrong, that’s about it) But we’ll see.

@nwoki
I’ll be amazed if anyone can tell you anything from this information! ( error 0xc0000005 is «Access violation error», so memory is being accessed wrong, that’s about it) But we’ll see.

I know. And that’s about it for the info i get from the application under windows. I can’t reproduce this problem on Linux. Anyone got any clues on how I can get more debug info for you guys?

A qt application I’ve made runs correctly on a windows system for some time, then it suddenly stops running (client says he didn’t do anything and that it just stopped working). Once this happens, the application cannot start anymore (tried reinstalling the app but no luck).

How long is «some time»? A few minutes? A few hours? A few days?

What do you mean by «the application cannot start anymore»? What happens when you try to start it?

Finally, how does the crash occur? Does it crash while your client is in the middle of using it, or does it crash at startup?

@nwoki Well it would be good to start with a windows vm development environment that you can reproduce the problem. That will let you attach to a debugger and get some useful information.

Another way is to build with map files and debug info. Then based on the crash/memory dump you can find which line of code your app crashed on. This can be daunting and a bit complicated if you’ve never done it before. And adding debug symbols may change the app enough that it «works» which doesn’t really help since you know there’s an issue but it gets masked by the debug binary.

Finally, this is why everything I write has massive amounts of logging. I even use kind of a «call stack» type thing in my logging code. So every function that is entered and exited gets a log message. This lets me narrow down a crash on a customer’s system with nothing more than a log file they provide. That isn’t helpful if you didn’t do it from the start though as it would take a lot of time. Something to note for the future.

If I had to throw out a complete guess, you probably have mixed Qt versions on the target system. Try using a dependency walker to see what Qt (and other) DLLs it is linking to and using. That is the usual culprit when something that worked before stops working with no update. It usually means a DLL got updated somewhere and broke it.

A qt application I’ve made runs correctly on a windows system for some time, then it suddenly stops running (client says he didn’t do anything and that it just stopped working). Once this happens, the application cannot start anymore (tried reinstalling the app but no luck).

How long is «some time»? A few minutes? A few hours? A few days?

A few days/1 week

What do you mean by «the application cannot start anymore»? What happens when you try to start it?

When launched the application doesn’t start. From the windows Event viewer i can see the application throw an error there but no window is ever presented. I don’t think the application ever gets to launch

Finally, how does the crash occur? Does it crash while your client is in the middle of using it, or does it crash at startup?

On startup. Doesn’t even show initial screen

Using the profiler as suggested by @ambershark I get the following.

This is the first time debugging a problem of this kind (I usually develop under linux). I see there are some problems «hooking modules». Might that be somewhere to start off from?

Hi, the profiler says the crash is inside dvr.exe and not in a Qtxxx dll.
So you could try using Process Monitor.
Start procmon.exe and set it to filter out all events except for your dvr.exe (that way you will not get swamped by thousands of events from other programs like explorer.exe etc.)
Then start dvr.exe and when it crashes, look in procmon.exe’s window to see what the last events were before dying.

@nwoki The hook module issues aren’t a problem. That is normal and you can ignore that.

If you can duplicate this crash on a virtual machine or on the customer’s machine then you could install a debugger (like WinDbg) and run the application in there to see what the backtrace shows. I’m a linux guy too so I’m not sure WinDbg will do what you need but it sounds like it should.

This would be equivalent to gdb ./dvr in linux and then when it crashes doing a bt . That should give you some insight as to what is crashing. If you can’t duplicate it on your machine you are stuck with adding logging (a lot of work), or doing the map file and debug info in your exe so you can find where the crash happened based on a crash log from the customer.

A quick update. I got the client to give me his computer for debugging next week. I’ll update you with the info on what @hskoglund and @ambershark advised to do. Thanks

@hskoglund Hi, finally got my hands on the client’s pc. This is what happens with ProcMon (hope I’m using it correctly. Not a power windows user.)

This is basically what happens when i launch the process and then veiw the process tree. For the events, I have this.

QtCharts having problems?

Hi, yeah if you run dvr.exe again a few times and it always crashes after loading the qtchartsqml2.dll, then it could be worthwhile to try a version of dvr.exe rebuilt without any Qt Charts functionality. Simplest would be to comment out those pieces of code, remove «QT += charts» the from the .pro file, rebuild dvr.exe and run the modified version on the client’s pc.

But first thing you should do on that client’s pc is to update the graphics driver, that might be an easier way to solve the problem 🙂

Did some more tests, as suggested, removed the QtCharts from the application and tried to force angle with

Without charts

Now the last thing it seems to load before crashing si the QWebProcess.exe file. I tried to run it by itself and it as visible in the process monitor. I then check the process when launched with Qt and I found this:

Might this have anything to do with the crash?

I’m starting to begin to think that it’s a problem related to the intel drivers of the card as i’ve found others with problems like mine here and here.

Plus, this is the only computer that presents this problem. My windows machine, and that of my collegues that have a dedicated graphics card, run the application without any fuss.

Using windows debugger, I get the following error

First time I get this sort of error. Anyone know what might be the cause for it?

Hi, that baadfood address in ecx is a fallback value for uninitialized objects on the heap, it could be that you’re trying to set the QAction text for a bad QWidget/OpenGL window. Again, this could mean that the Intel graphics driver needs to be updated.

So, turns out that the only error message that was telling the truth was the one regarding the QAction : Qt5Widgets!QAction::setText+0x1: .

What was happening was the following:

I’ve implemented a «Recent files» QMenu where i set the last 5 recent files used by the client. What happened in this particular case was that the client removed some recent files that were stashed by my application (their path url) and so when I want to load them into the menu with:

the application crashed.

What threw me off was the first part of the debug message

which led me to think it was a problem concerning the graphical driver of the client as he told me he had done some updates lately and that the access error was related to the QWidgets.dll file.

Once I fixed that, the application went back to normal. Thankyou @ambershark and @hskoglund (you’re last comment helped me find the problem) for your help. I’ve also learned a few things on debugging under windows (i’m a linux guy).

OOI. What actually crashed? The code you show? Do you mean m_recentFilesActions.at(i) was nullptr /invalid?

was the culprit as the QFileInfo was not being created seeing that the recent file had been moved.

@nwoki
I really do not understand this, for two reasons:

When you try to create a QFileInfo(QString filepath) it does not fail if the path does not exist. If it did, there would be no point in having e.g. a QFileInfo::exists() function. AFAIK, the QFileInfo methods treat the filepath as a string to parse to produce results for extracting segments; they only try to access the file when a function which needs to do so is called. I therefore assume QFileInfo(recentFiles.at(i)).fileName()); would return the filename part of whatever you passed in.

Even if that were not true, then either it would throw some exception possibly or it would return, say, an empty string for the filename. You would pass that to your rf->setText() , and whatever that did it would not «crash» on trying to set some text.

I should be obliged if a Qt expert would correct me if the above is not true? Otherwise I do not see how in itself it would lead to the behaviour you have previously shown, which is why I asked.

Hope this helps you.

@Limer I had no idea a non-GUI thread was involved!

@nwoki I’m with @JonB on this . I don’t understand why it’s failing.

QFileInfo fi(«»).fileName() for instance should not crash at all. It’s perfectly valid. So if your recents list had a cleaned up file it shouldn’t have mattered at all.

I only typically have linux environments to test with and it works fine in linux (but you already knew that). So if it fails in windows that is a Qt bug not a bug in your software. Assuming it’s a crash in QFileInfo().fileName() which at worst should return an empty string, not crash.

Glad you got it working but it may be a «fake» fix since there is no reason that should have crashed in windows or elsewhere.

There was no mention in this posting about a non-gui thread at all. Not sure where you got that idea.

Источник

Qt5 application crashed with error 0xc0000005

This is very interesting crash and I think it should be considered as Qt bug. This problem arise only under very special circumstances. But one after another.

You will identify this problem when your application stopped/exited immediately after the start without any visible error message. It looks like the application isn’t executed at all. When you check application log (Computer -> manage -> Event viewer -> Windows logs -> Application), you will see Error logs:

The most interesting part of this log is crash location: ntdll.dll

At first sight it seems like some problem inside the windows. But the opposite is true, the problem (as almost always) is inside your app ;-).

As the next step, you can try to debug this executable via Visual Studio to see what happens inside. Simply open executable as project together with .pdb files and execute it. Now you can see that application is correctly executed but crashes as soon as it touches Qt library. The location of crash is inside ntdll.dll in RtlHeapFree() function.

So the problem is inside the Qt, right? Almost true, but not for the 100%. When I tried to run this application on computers of my colleagues, everything works ok. So why the application doesn’t work on my computer too?

Resolution

The problem is in new Qt5 plugin system. Besides the common Qt5*.dll files which are loaded immediately after the application start, Qt5 is also loading plugins/platform-plugins dynamically when the application is executed. To locate this plugins, Qt5 uses following method to identify directories where to search for plugins:

For some strange reason this library returns as first directory path where Qt5 libraries were compiled and after that location based on the executable. So if your Qt5 path is C:Qt5, this will be the first path where all plugins are searched for, no matter if the correct version of plugin is located in APPplugins or APPplatforms. I think this is serious bug in Qt5.

Where is the problem?

And here we’re getting to the core of the whole problem.

If application is compiled on computer with one compiler and used on second computer which contains the same path to which original computer has installed Qt, the application will load all plugins from your folder instead of itself folder.

In case your computer will contain different version of Qt, different compiler or different platform, application loads incorrect libraries and crashes. Completely, silently and without easy way to determine what’s wrong.

Solution?

The solution is simple, but it isn’t achievable from outside of the Qt library. It would be necessary to Qt as first tried to load libraries from application directory. And only if no plugins were found in application directory, the application would try to search for plugins in Qt directory.

Qt change solution

The simplest way how to fix this issue inside the Qt library would be to rename/update appendApplicationPathToLibraryPaths function to prependApplicationPathToLibraryPaths and change

InApp solution

Unfortunately it isn’t possible to simply change this behavior from your app. All of these operations happen directly in QCoreApplication constructor so if you try to change it after, it’s too late.

Источник

Hello everyone,

I have made small computer game using QT in CLion.
At beginning I show main menu with four rect items created as buttons, I connect it to some slots f.e start() — slot which start game, showHelp() — showing help informations, showScores() — top scores and the last one is quit connected to close() slot.

Let me explain how my code works — I running for first time application then all items in the main menu working. When I click the start button it bring me to start method and all code from this method working as I wish.
If the player health is equal 0 or lower program showing gameOverWindow() and in this window have two buttons. One is playAgain and this button restarting game, next one moving to main menu — this menu which are displayed at start of my program.

The problem that arises is when I click play again button it successful restart game, but sometimes it crashing my application at showGameOverWindow or after when I back to mainMenuWindow with those error information:

pure virtual method called terminate called without an active exception

but not always, sometimes it’s this exit code:

Process finished with exit code -1073741819 (0xC0000005)

When it doesn’t crash after that cases program will always crash after clicking any button in mainMenu without play game button.

Any help would be appreciated

Source code:

Code which checking health is under or equal 0

//some useless code before
if (game->health->getHealth() <= 0){
int score = game->score->getScore();
                game->scene->clear();
                game->ShowGameOverWindow(score);
}
To copy to clipboard, switch view to plain text mode 

ShowGameOverWindow

void Game::ShowGameOverWindow(int score){
    setBackgroundBrush(QImage("../Sources/Pictures/gameover.png"));
float height = window()->height();
float width = window()->width();
    drawPanel(0,0,860,600,Qt::black,0.35);
    drawPanel(width/4+30,height/4,400,400,Qt::lightGray,0.75);
    backMenuButton = new Button(QString("../Sources/Pictures/Menu/ok-inactive.png"),
QString("../Sources/Pictures/Menu/ok-active.png"));
int qxPos = width-320;
int qyPos = height-110;
    backMenuButton->setPos(qxPos, qyPos);
connect(backMenuButton, SIGNAL(clicked()), this, SLOT(displayMainMenu()));
    scene->addItem(backMenuButton);
    playAgainButton = new Button(QString("../Sources/Pictures/Menu/again-inactive.png"),
QString("../Sources/Pictures/Menu/again-active.png"));
int pxPos = width/3-30;
int pyPos = height-110;
    playAgainButton->setPos(pxPos, pyPos);
    playAgainButton->setSize(200,51);
connect(playAgainButton,SIGNAL(clicked()), this, SLOT(start()));
    scene->addItem(playAgainButton);
}
To copy to clipboard, switch view to plain text mode 

start game slot

void Game::start() {
    scene->clear();
    scene->setSceneRect(0,0,800,600);
    setFixedSize(800,600);
    setBackgroundBrush(QImage("../Sources/Pictures/gameBackground.png"));
    player = new Player();
    player->setFocus();
    player->resetPos();
    scene->addItem(player);
    score = new Score();
    score->resetScore();
    score->setPos(score->x()+600, score->y()+9);
    scene->addItem(score);
    health = new Health();
    health->resetHealth();
    health->setPos(health->x()+380, health->y()+9);
    scene->addItem(health);
if(!mainTimer->isActive()) {
connect(mainTimer, SIGNAL(timeout()), this, SLOT(mainLoop()));
        mainTimer->start(0);
}
    counting(1000);
auto * timerHurdle = new QTimer();
QObject::connect(timerHurdle,SIGNAL(timeout()),player,SLOT(spawnHurdle()));
    timerHurdle->start(2000);
auto * timerHeart = new QTimer();
QObject::connect(timerHeart,SIGNAL(timeout()),player,SLOT(spawnHeart()));
    timerHeart->start(10000);
}
To copy to clipboard, switch view to plain text mode 

Display main menu

void Game::displayMainMenu() {
    scene->clear();
    scene->setSceneRect(0,0,1030,768);
    setFixedSize(1030,768);
    setBackgroundBrush(QImage("../Sources/Pictures/Menu/background.png"));
// buttons and properties
    playButton = new Button(QString("../Sources/Pictures/Menu/start-inactive.png"),
QString("../Sources/Pictures/Menu/start-active.png"));
int bxPos = playButton->boundingRect().width()/8 + 3;
int byPos = 380;
    playButton->setPos(bxPos, byPos);
connect(playButton,SIGNAL(clicked()), this, SLOT(start()));
    scene->addItem(playButton);
    scoreButton = new Button(QString("../Sources/Pictures/Menu/scores-inactive.png"),
QString("../Sources/Pictures/Menu/scores-active.png"));
int sxPos = scoreButton->boundingRect().width()/8 + 3;
int syPos = 450;
    scoreButton->setPos(sxPos, syPos);
connect(scoreButton,SIGNAL(clicked()), this, SLOT(showScores()));
    scene->addItem(scoreButton);
    helpButton = new Button(QString("../Sources/Pictures/Menu/help-inactive.png"),
QString("../Sources/Pictures/Menu/help-active.png"));
int hxPos = helpButton->boundingRect().width()/8 + 3;
int hyPos = 520;
    helpButton->setPos(hxPos, hyPos);
connect(helpButton,SIGNAL(clicked()), this, SLOT(showHelp()));
    scene->addItem(helpButton);
    quitButton = new Button(QString("../Sources/Pictures/Menu/quit-inactive.png"),
QString("../Sources/Pictures/Menu/quit-active.png"));
int qxPos = quitButton->boundingRect().width()/8 + 3;
int qyPos = 610;
    quitButton->setPos(qxPos, qyPos);
connect(quitButton,SIGNAL(clicked()), this, SLOT(close()));
    scene->addItem(quitButton);
    backButton = new Button(QString("../Sources/Pictures/Menu/back-inactive.png"),
QString("../Sources/Pictures/Menu/back-active.png"));
int backxPos = scene->width()/2 - 40;
int backyPos = 610;
    backButton->setPos(backxPos, backyPos);
connect(backButton,SIGNAL(clicked()), this, SLOT(displayMainMenu()));
    scene->addItem(backButton);
    parchmentImage = new QLabel();
QPixmap img("../Sources/Pictures/Menu/paper.png");
    parchmentImage->setPixmap(img);
double x = img.width();
double y = img.height();
    parchmentImage->setGeometry(300,250,x,y);
    scene->addWidget(parchmentImage);
    info = new TextInformation();
    info->setPosition(300,270);
    scene->addItem(info);
if(backButton->isVisible()) { scene->removeItem(backButton); }
if(info->isVisible())       { scene->removeItem(info); }
    info->setProperties(Qt::black,"arial",16,300,270);
    parchmentImage->setHidden(true);
    playButton->setEnabled(true);
    scoreButton->setEnabled(true);
    helpButton->setEnabled(true);
    quitButton->setEnabled(true);
}
To copy to clipboard, switch view to plain text mode 

If the problem is too hard to imagine I can make short video to show you how I really looks or even paste more source code.

Описание вопросов

• В гибридном программировании VS и Qt я столкнулся с проблемой 0xC0000005, смущенным днем, теперь прилагается решение.

описание проблемы

Решение

• Поместите UI :: youclassname * ui; заменить его здесь в пользовательский интерфейс :: youclassname ui;，То есть использовать обычные переменные, не используйте указатели
• Что такое правда, неясно

Ручка блог:Qt Binding интерфейс пользовательского интерфейса и четырех методов класса Qt

Qt Binding интерфейс пользовательского интерфейса и четырех методов класса Qt

/ **************************** QT заголовочный файл объявляет пространство имен ************ ***** *********** /

namespace Ui {
    class Widget;
}


public:
    explicit Widget(QWidget *parent = 0);
private:
    Ui::Widget *ui;


Widget::Widget(QWidget *parent) :
    QWidget(parent),
    ui(new Ui::Widget) 
    {...}


ui->setupUi(this);
/ / / / Должен быть после setupui
ui->pushButton->setToolTip("666");


/ *************************************************** *************************************************************** *************************** ******************** /

private:
    Ui::MyForm form;


form.setupUi(this); 
form.btnDel->setEnabled(false);


/ *************************************************** ************************** *************** /

class Form : public QWidget, private Ui::Form
{public:
    explicit Form(QWidget *parent = 0); 
	...  
}

   setupUi(this); 
   pushButton->setToolTip("666");


/ ***************************** vs & Qt Как использовать: ************* *************** /

#include "ui_sokit.h"  
... 
class Sokit :public QWidget
{
	Q_OBJECT
public:
	explicit Sokit(QWidget *parent = 0);
private:
	Ui::sokit ui;// значение ObjectName Sokit здесь - это значение ObjectName интерфейса дизайнера.  
	......
}


#include "sokit.h"
Sokit::Sokit(QWidget *parent) :QWidget(NULL)
{ 
	ui.setupUi(this);   
	ui.label->setText("666");// Обратите внимание на разницу между этим и Qtcreater
	...... 
}

Есть также хороший пост

VS2013 Компилированные программы QT Невозможно найти информацию о отладке

Qt Creator Project в Project Project

QT5.6 + OpenC2.49 + VS2015 сгенерированный метод исполняемого пакета EXE

Интерфейс QT закрывает главное окно. Если коробка QDialog не закрывается, программа не может выйти.