QMessageBox closes application

ODБOï

hi
@hobbyProgrammer said in connect() keeps crashing:

connect

most likely this will not solve the crash but its better to use New Signal Slot Syntax

 connect(this, &MyClass::customContextMenuRequested, this, &MyClass::showContextMenu);

marcbf

As @jsulm said, it's probably your slot that crashes. The reason for that assumption is that you don't specify a connection type and the default is a Qt::AutoConnection which in turn means a Qt::DirectConnection. That means your slot is called as soon as it is triggered. Perhaps something isn't quite ready at that point? Try specifying Qt:QueuedConnection as the connection type and see if that helps.

As @LeLev points out you may be better off using the new signal/slot syntax as long as there isn't any overloaded signal in place. If you keep using the old signal/slot syntax (perfectly valid) you may want to change the parameter type(s) to the pure non-qualified type in your connect statement (and only there). That is, instead of specifying const QPoint&, just specify QPoint. Also, if you have more than one parameter make sure that there's no space before or after the comma.

hobbyProgrammer

@LeLev said in connect() keeps crashing:

connect(this, &MyClass::customContextMenuRequested, this, &MyClass::showContextMenu);

I tried this, but it still doesn't come back from the showContextMenu. I inserted a qDebug() at the end of showContextMenu and that one does show up in the debugger, but the qDebug() i've put after the connect() doesn't show up in the debugger.

JonB

@hobbyProgrammer
There is something very odd here. If it genuinely does not execute the line after the connect() as you say, then (presumably) the connection would not be made so the slot would never be called and you would not see showContextMenu() being called. Have a look again at your code/debug output, use a debugger breakpoint, etc.

jsulm

@hobbyProgrammer Then please show showContextMenu code or a stack trace, else we can only guess...
The thing is: connect() does not call showContextMenu, it just connects the signal to the slot.

hobbyProgrammer

@jsulm It seems to print the qDebug() line before executing the connect(). And the app closes in the qeventloop.cpp.

    while (!d->exit.loadAcquire())
        processEvents(flags | WaitForMoreEvents | EventLoopExec);

I have no idea why it stops there.

hobbyProgrammer

@jsulm it also stops whenever I save a file. The saving part works perfectly, but afterwards it just closes down the app and it seems to be the same mystery as the showContextMenu.
I would like to think that it's the connect function, since they both use connect().
However I've connected about 20 actions like this and only 2 seems to close the app. I would expect them all to close down the app if it were the connect() function.

jsulm

@hobbyProgrammer As I said: connect() does not call the slots.
Why don't you simply use debugger to see where exactly it crashes?

hobbyProgrammer

@jsulm As I said:
it closes/crashes in the qeventloop.cpp.

    while (!d->exit.loadAcquire())
        processEvents(flags | WaitForMoreEvents | EventLoopExec);

But I have no clue how to prevent this

JonB

@hobbyProgrammer
@jsulm will know better than I, but I wouldn't have thought connect() would even call processEvents()/the main event loop?

hobbyProgrammer

@jsulm @JonB Whenever I use the debugger I don't even get the showContexyMenu(), but when I don't open in debugger, I do get the contextMenu...

jsulm

@hobbyProgrammer Does it crash if you do not connect the slot?
And it would be helpful if you would post the stack trace after crash.

Christian Ehrlicher

@hobbyProgrammer said in connect() keeps crashing:

Whenever I use the debugger I don't even get the showContexyMenu(),

So what's the backtrace?

hobbyProgrammer

@jsulm @Christian-Ehrlicher

I'm not really familliar with the debugger... Does this provide the information you need?

jsulm

@hobbyProgrammer If you post screen shots you should at least make sure the function signature on the bottom-right side are readable...

hobbyProgrammer

@jsulm
is this better?

JonB

@hobbyProgrammer
It would be better if we could read the full function signatures at the bottom right, instead of left-truncated! Can't you drag the column resizer so we can see the full function name? You can make columns like Condition or Ignore much smaller.

Pl45m4

@hobbyProgrammer said in connect() keeps crashing:

qv.at(i)

It looks like you've created your vector on stack. What exactly does your slot do? Which vars do you access / try to access there?
If the connection fails, you would get an explicit warning / error message (which is obviously not the case)

I'm sure, that it crashes because you did something wrong before or inside your slot function.

hobbyProgrammer

@Pl45m4 Hi, I've found why it closes the app (sort of).
I have a few screens before this one. After going through those screens, you'll end up at this screen.
Whenever I only open this screen, it works perfectly, but when I open the screen through a different screen, it closes after a certain action.
Those other screens are hidden whenever a new screen is shown.

I still don't know why it closes.

Pl45m4

@hobbyProgrammer said in connect() keeps crashing:

I've found why it closes the app (sort of).

@hobbyProgrammer said in connect() keeps crashing:

I still don't know why it closes

Hm.... :D

@hobbyProgrammer said in connect() keeps crashing:

I have a few screens before this one

What kind of screens? You mean, if you are doing something, then it works but if you do something else (different action), then it crashes?

YOU programmed it, so you must know (should know) best, WHAT you did ;-)
Anybody else can just guess, if you make vague descriptions...

What does the "crash" look like? Any exception / error message or is it just terminating your process?