QMetaObject::activate() causing Segmentation fault
-
wrote on 19 Oct 2023, 10:56 last edited by
Hi,
My application suddenly crashed after a few days with the following stack trace:
Program terminated with signal SIGSEGV, Segmentation fault. #0 0x75fbe1b5 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5This is the extract of the core dump and the only line referring to the crash.
I figured it has something to do with a signal to a slot of an object that no longer exists. But I am not sure how this is even possible.
Had no success reproducing the crash until now.I am using Qt 5.9.6. Is that maybe a know issue for this version?
Regards,
Drembo -
Hi,
My application suddenly crashed after a few days with the following stack trace:
Program terminated with signal SIGSEGV, Segmentation fault. #0 0x75fbe1b5 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5This is the extract of the core dump and the only line referring to the crash.
I figured it has something to do with a signal to a slot of an object that no longer exists. But I am not sure how this is even possible.
Had no success reproducing the crash until now.I am using Qt 5.9.6. Is that maybe a know issue for this version?
Regards,
DremboHi,
Do you know which object triggered that exactly ?
By the way, 5.9.6 is more than obsolete, you should really consider updating to a more recent version.
-
wrote on 23 Oct 2023, 08:58 last edited by
Hi,
I don't know what triggered it. There weren't any additional lines in the stack trace. I thought maybe it is a known 5.9.6 issue.
Of course, I am considering moving to a newer Qt version. -
You can also check the bug report system to find if there's something related to that.
1/4