<![CDATA[Is this object destruction failure?]]>Why does the following program crash when trying to exit the program?

#include <QApplication>
#include <QLayout>
#include <QLabel>

int main(int argc, char *argv[]) {
    QApplication app(argc, argv);
    QWidget appWidget;

    QLabel lblA("A");
    QGridLayout layG;
    layG.addWidget(&lblA, 0, 0);

    QLabel lblB("B");
    QVBoxLayout totalLayout;
    totalLayout.addLayout(&layG);
    totalLayout.addWidget(&lblB);

    appWidget.setLayout(&totalLayout);
    appWidget.show();

    return app.exec();
}

but if you dynamically allocate memory for just one of layG or totalLayout layouts, it won't crash.
what is happening here?

]]>https://forum.qt.io/topic/164031/is-this-object-destruction-failureRSS for NodeSun, 19 Apr 2026 00:25:58 GMTFri, 02 Jan 2026 21:41:00 GMT60<![CDATA[Reply to Is this object destruction failure? on Sat, 03 Jan 2026 00:07:50 GMT]]>QObjects destroy their children when they are destroyed, and a layout is automatically the parent of any sub-layout added to it.

Stack objects are destroyed in opposite order to their creation, so totalLayout gets destroyed first, and it also destroys layG since it is its child object in the QObject hierarchy. The next in order is lblB, but after it layG gets destroyed, but it was already deleted so it is a use after free violation and a crash.

Dynamically allocating (and leaking) either layout prevents automatic destruction of it so avoids the scenario.

]]>https://forum.qt.io/post/835126https://forum.qt.io/post/835126Sat, 03 Jan 2026 00:07:50 GMT<![CDATA[Reply to Is this object destruction failure? on Sat, 03 Jan 2026 08:42:02 GMT]]>Don't create widgets and especially layouts on the stack at all to avoid such problems.

]]>https://forum.qt.io/post/835134https://forum.qt.io/post/835134Sat, 03 Jan 2026 08:42:02 GMT<![CDATA[Reply to Is this object destruction failure? on Sat, 03 Jan 2026 00:52:41 GMT]]>I get it. but actually QLayout is not responsible for destroying any QWidget that is added to it. QLayouts only destroy QLayouts that are added to them. QWidgets cannot be a "child" of QLayouts. here, totalLayout is responsible for removing layG object, which is its child. So here what actually causes the crash is as follows when stack unwinds at the end:
First, totalLayout's destructor is called.
Second, in the destructor, totalLayout evokes "delete" operator on layG (cause totalLayout is responsible for removing layG as its child)
and here is the problem. layG is stack-allocated and calling "delete" operator on a stack-allocated object is not valid.

So, if we allocate even one of them on the heap, in both scenarios it obviously would resolve this problem, one by memory leaking and the other by properly deallocating object.

This is true for the widgets too. the only thing different, is that setLayout() function in widgets makes the widget responsible for the life-time of the QLayouts.

Changing the order of Layou creations, in this case matters. If I were to create totalLayout before layG, the crash wouldn't have happened. cause layG would've been properly destroyed before totalLayout tried to evoke "delete" operator on it. Though, I'm not sure how it's handled in Qt.

]]>https://forum.qt.io/post/835127https://forum.qt.io/post/835127Sat, 03 Jan 2026 00:52:41 GMT<![CDATA[Reply to Is this object destruction failure? on Sat, 03 Jan 2026 00:07:50 GMT]]>QObjects destroy their children when they are destroyed, and a layout is automatically the parent of any sub-layout added to it.

Stack objects are destroyed in opposite order to their creation, so totalLayout gets destroyed first, and it also destroys layG since it is its child object in the QObject hierarchy. The next in order is lblB, but after it layG gets destroyed, but it was already deleted so it is a use after free violation and a crash.

Dynamically allocating (and leaking) either layout prevents automatic destruction of it so avoids the scenario.

]]>https://forum.qt.io/post/835126https://forum.qt.io/post/835126Sat, 03 Jan 2026 00:07:50 GMT