Actions
Bug #13585
closedSegfault on internal path navigation with submenus
Start date:
02/26/2025
Due date:
% Done:
100%
Estimated time:
Description
In case we have a main WMenu
with setInternalPathEnabled()
, and submenus added to that main menu via WMenu::addMenu()
, each also with setInternalPathEnabled()
, we encounter a segfault.
This occurs when navigating to the item immediately upon loading the menu, i.e. when the current internal path matches the one being defined by the stack of WMenu
s.
Here, we then assume that the path would lead to a WMenu
that has some content, and load the content. However, in case of a submenu, no content is defined, yet expected.
A case ought to catch that no content is set on the item.
Updated by Matthias Van Ceulebroeck about 2 months ago
- Status changed from InProgress to Review
- Assignee deleted (
Matthias Van Ceulebroeck)
Updated by Matthias Van Ceulebroeck about 1 month ago
- Assignee set to Marnik Roosen
Updated by Matthias Van Ceulebroeck about 1 month ago
- Status changed from Review to Implemented @Emweb
- Assignee changed from Marnik Roosen to Matthias Van Ceulebroeck
- % Done changed from 0 to 100
Updated by Matthias Van Ceulebroeck 25 days ago
- Status changed from Implemented @Emweb to Implemented @Test
Updated by Matthias Van Ceulebroeck 14 days ago
- Status changed from Implemented @Test to Closed
Updated by Matthias Van Ceulebroeck 9 days ago
- Related to Bug #13701: Crash with Menu with StackedWidget added
Actions