Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.10.1, 5.11.1
-
-
81e298a51d08c510457b4a26b37c0d4aac5eba65
Description
If tab widget has child items, and the next child item in tab order after the tab widget itself, is the last child item in the tab's children list, destructing that widget crashes.
Steps to reproduce:
- Run attached sample
- Close the application
- EXPECTED: Application destructs properly
- ACTUAL: Application crashes (see attached image)
The crash can be prevented by switching the tab order of the two inner buttons (2 and 3) in .ui file:
From
<tabstops> <tabstop>pushButton_4</tabstop> <tabstop>tabWidget</tabstop> <tabstop>pushButton_3</tabstop> <tabstop>pushButton_2</tabstop> </tabstops>
To
<tabstops> <tabstop>pushButton_4</tabstop> <tabstop>tabWidget</tabstop> <tabstop>pushButton_2</tabstop> <tabstop>pushButton_3</tabstop> </tabstops>
Or by simply moving the pushButton_3 child item before the pushButton_2 child item in tab_2's widgets list.
Attachments
Issue Links
- duplicates
-
QTBUG-68393 Heap corruption during deferred widget destruction
- Closed