My program start to crash because of MessageBox

[JonB]

@Engelard

Exactly, i can't backtrace it because there is nothing to trace rly, just a small function...

Yes, you can, and should. Run the program under the Qt Creator debugger. Assuming it really does "crash", at that point the debugger should catch it. Go to the "stack trace" (or "back trace") window at that point, and paste here whatever information it does have.

BTW, you can probably also try

QMessageBox::information(nullptr, "ERROR", text);

and see whether that too "crashes" or not.

[mrjj]

Hi
Just start the app in debug mode. And then make it crash.
It should show in call stack what it was doing before it died.

Also, just for test add a new button and call
err("TEST");
to see if that triggers the crash.
If not, it must have something to do with the surrounding code from where you
use err() . maybe a dangling pointer.

[J.Hilk]

@Engelard what os and qt version is this?

I had some issues like this under ios and 5.12.0 went away with one of the later updates

also do you call processEvents() somewhre inside your code?
the static call to QMessageBox spins its own QEventLoop. That on combination with processEvent calls can cause very strange behaviour and crashes.

[JonB]

@J.Hilk

QMessageBox::information();

just as that statement, blocks, spins its own loop, and does not return till the user has pressed a button, correct or not? So you can't be calling processEvents() elsewhere in your own code, unless you're doing something really odd, is that not right?

[Christian Ehrlicher]

@JonB said in My program start to crash because of MessageBox:

is that not right

When there is a timer which is executed while the message box is shown and in the slot you call processEvents() you will get likely into trouble.

[J.Hilk]

@JonB Just because you call start on an other event loop doesn't mean your original one simply stops.

You get a general setDisbaled on your MainApplication Ui, everything else is still going on normally.

Take this example, based on what @Christian-Ehrlicher said:

int main(int argc, char *argv[])
{
    QApplication a(argc, argv);

    QTimer alive;
    QObject::connect(&alive, &QTimer::timeout, []()->void{qDebug("Alive");});
    alive.start(500);

    QPushButton btn;
    btn.show();
    QObject::connect(&btn, &QPushButton::clicked, []()->void{
                         QMessageBox::information(nullptr, QString("Error"), QString("Some Error Text"));
                     });

    return a.exec();
}

[JonB]

@Christian-Ehrlicher , @J-Hilk
Yep, fair enough, thank you. I was not thinking about a timer. And nor about a timer calling processEvents(), which I would think would not be advisable!

We shall see whether the OP's problem stems from this.

[Engelard]

@mrjj said in My program start to crash because of MessageBox:

Just start the app in debug mode. And then make it crash.
It should show in call stack what it was doing before it died.

It shows numerous windows like this:

What is all mean?

@J.Hilk said in My program start to crash because of MessageBox:

also do you call processEvents() somewhre inside your code?

No

[aha_1980]

@Engelard said in My program start to crash because of MessageBox:

It shows numerous windows like this:

These are uninteresting.

We need the call stack (also called stack trace, or backtrace)

[mrjj]

Hi
the call stack / trace it looks like this

[Engelard]

[mrjj]

@Engelard
and that is from it crashes ?

[Engelard]

@mrjj If i comment out my line

QMessageBox::information(nullptr, "ERROR", "trtrtr");

Debugger will be absolutely empty. When i use this static function of messBox, it give me such output.

[Engelard]

Hey i just found that it work well if i put it in the constructor, so it crashes only when it in my other functions, strange.

UPDATE:

Here is info for everyone. Yesterday, i noticed that the app not just crashed, it crashed like.. twice, and all my app mostly about the use of "pressed" and "released" SLOTs of the buttons. I removed usage of release slot, and now app do just single crash. Here is how "release button" chain looks like:

void MainWindow::on_button_Q_released()
{
    //lightRestore(currentButton);
}

And here is that only function which it use:

void MainWindow::lightRestore(QPushButton *lamp)
{
    lamp->setStyleSheet("QPushButton{color: white;background-color: rgb(35,35,35);border-style: outset;border-width: 2px;border-radius: 15px;border-color:  black;font: bold 12px;}");
}

[hskoglund]

Hi, if I read the trace correctly, the user presses the button_G, that functions calls mainJourney() which issues the QMessageBox() call.
Could you show the code for mainJourney()?

[J.Hilk]

@Engelard said in My program start to crash because of MessageBox:

currentButton

seems like currentButton is no longer a valid QPushButton-Pointer,

If you have a pointer member variable, you should make sure that you always set it to a nullptr when the pointed to object is destroyed/invalid.
And always check against that before accessing it:

void MainWindow::lightRestore(QPushButton *lamp)
{
    if(lamp)
        lamp->setStyleSheet(...);
}

[Engelard]

@hskoglund said in My program start to crash because of MessageBox:

Could you show the code for mainJourney()?

No, that stuff is too big, it called from pressButton SLOT, above much simplier and compact example of release, it does the same crash.

[Engelard]

@J.Hilk nice advice, tnx. But it valid(without that messageBox stuff everything works perfectly), i added if-check line. Nothing it changed(2nd crash exist).

UPDATE:

If i put messageBox AFTER assignment of that button - will be no crashes, but also it is not possible to hold the button(because this messageBox take over priority and it is now main waindow).

void MainWindow::on_button_Q_pressed()
{
    currentButton = mainJourney('Q');
    lightSet(currentButton);
    QMessageBox::information(nullptr, "ERROR", "trtrtr");
}

[Engelard]

Oh, finally! With the help of @J-Hilk i realised what was wrong.

1. add if-cheks in "lights" functions.
2. assign currentButton to nullptr in the constructor. (i mistakenly thought that created pointers of the objects without assignment by default nullptr)

Now no crashes. Tnx @J-Hilk !