This crash occurred out of the blue sky with Qt Creator master/2.7/Qt 5:

To reproduce:

• Open some code file
• Open context menu, hover over menu options without invoking any
• Repeat several times, observe crash
  (if it doesn't occur, over over sth else, say files combo without changing anything).

Discussion:

When hovering over the menu items, QAccessibleMenuItems are created that are associated with the (persistent) action from Qt Creator's action manager whose 'owner' is the CppMenu, which is deleted after use.

A few invocations of the menu later, one sees that the debug in QAccessibleMenuItem::owner() of that action still shows the long-gone menu from a previous invocation and then crashes.

That of course raises the question, how did this ever work, keeping actions around and adding them to several menus being a common technique. Either sth in QAccessibleMenuItem is completely borked or some QObject::disconnect severes a connection to some destroyed signal that would remove the QAccessibleMenuItem, but I cannot see that.

Any help welcome.