<![CDATA[Memory management in the calendarwidget example. Is there are memory leak?]]>Hello, this is my first time posting here!

I am new to C++ and Qt and I was looking at the example source code. Specifically, this file:

https://github.com/qt/qtbase/blob/dev/examples/widgets/widgets/calendarwidget/window.cpp

and this member function:

void Window::createPreviewGroupBox()
{
    previewGroupBox = new QGroupBox(tr("Preview"));

    calendar = new QCalendarWidget;
    calendar->setMinimumDate(QDate(1900, 1, 1));
    calendar->setMaximumDate(QDate(3000, 1, 1));
    calendar->setGridVisible(true);

    connect(calendar, &QCalendarWidget::currentPageChanged,
            this, &Window::reformatCalendarPage);

    previewLayout = new QGridLayout;
    previewLayout->addWidget(calendar, 0, 0, Qt::AlignCenter);
    previewGroupBox->setLayout(previewLayout);
}

previewGroupBox, calendar and previewLayout are naked pointers to of type QGroupBox* QGridLayout* and QCalendarWidget*. My question is: When and where is the memory allocated using new released? Those objects have no parent to delete them and delete is not called anywhere is the example code.

Thanks in advance!

]]>https://forum.qt.io/topic/133938/memory-management-in-the-calendarwidget-example-is-there-are-memory-leakRSS for NodeThu, 14 May 2026 02:00:29 GMTSat, 29 Jan 2022 10:52:04 GMT60<![CDATA[Reply to Memory management in the calendarwidget example. Is there are memory leak? on Sat, 29 Jan 2022 11:26:06 GMT]]>@dgrigoro
When you addWidget() or setLayout() the objects all go into the widget hierarchy --- previewGroupBox here --- and you'll see parent get set. So those now belong to their parent hierarchy and get disposed with that.

The previewGroupBox is currently indeed orphaned. To use this method one would either add that into the widget hierarchy here or return it from the function so the caller can do that. In fact looking at the link it's a member variable, so it doesn't get lost, and the caller goes layout->addWidget(previewGroupBox), so that's how it gets connected.

If you haven't already done so, you'll want to read https://doc.qt.io/qt-5/objecttrees.html & https://doc.qt.io/qt-5/layout.html.

]]>https://forum.qt.io/post/700660https://forum.qt.io/post/700660Sat, 29 Jan 2022 11:26:06 GMT<![CDATA[Reply to Memory management in the calendarwidget example. Is there are memory leak? on Sat, 29 Jan 2022 11:50:49 GMT]]>@JonB Thank you! It's all clear now :)

]]>https://forum.qt.io/post/700661https://forum.qt.io/post/700661Sat, 29 Jan 2022 11:50:49 GMT<![CDATA[Reply to Memory management in the calendarwidget example. Is there are memory leak? on Sat, 29 Jan 2022 11:26:06 GMT]]>@dgrigoro
When you addWidget() or setLayout() the objects all go into the widget hierarchy --- previewGroupBox here --- and you'll see parent get set. So those now belong to their parent hierarchy and get disposed with that.

The previewGroupBox is currently indeed orphaned. To use this method one would either add that into the widget hierarchy here or return it from the function so the caller can do that. In fact looking at the link it's a member variable, so it doesn't get lost, and the caller goes layout->addWidget(previewGroupBox), so that's how it gets connected.

If you haven't already done so, you'll want to read https://doc.qt.io/qt-5/objecttrees.html & https://doc.qt.io/qt-5/layout.html.

]]>https://forum.qt.io/post/700660https://forum.qt.io/post/700660Sat, 29 Jan 2022 11:26:06 GMT