Additional info:
I put a BP on FMenuStack::DismissInternal() at the point in time where the menu item is clicked. It’s being called twice - whether that’s the bug or not I do not have enough context currently to say, however it matches the seen behavior that on the first call we have 3 entries in ‘Stack’:
Stack
Num=3
[0]: Ptr=0x000001e5d13b4f40, SharedRefs=2, WeakRefs=3, Object={Window=Ptr=0x000001e545ac7580, SharedRefs=1, WeakRefs=9, Object={MoveResizeZone=-842150451 MoveResizeStart={X=-431602080. Y=-431602080. } MoveResizeRect={Left=-1.00000000 …} …} }
Ptr=0x000001e5eb6f8280, SharedRefs=2, WeakRefs=3, Object={Window=Ptr=0x000001e5f419d600, SharedRefs=1, WeakRefs=9, Object={MoveResizeZone=-842150451 MoveResizeStart={X=-431602080. Y=-431602080. } MoveResizeRect={Left=-1.00000000 …} …} }
[2]: Ptr=0x000001e5a4e82140, SharedRefs=2, WeakRefs=3, Object={Window=Ptr=0x000001e5f410c100, SharedRefs=4, WeakRefs=28, Object={MoveResizeZone=-842150451 MoveResizeStart={X=-431602080. Y=-431602080. } MoveResizeRect={Left=-1.00000000 …} …} }
[Raw View]: {AllocatorInstance={Data=0x000001e544bc0580 {…} } ArrayNum=3 ArrayMax=4 }
Once DismissInternal() has completed Stack is empty. Then badness seems to ensue when it is called again for the same object (with what looks to be an identical call-stack) and runs off the beginning of the zero sized Stack collection:
Stack
Empty
[Raw View]: {AllocatorInstance={Data=0x0000000000000000 } ArrayNum=0 ArrayMax=0 }
Hope this helps
-San