Changes between Initial Version and Version 1 of Ticket #17842, comment 2
- Timestamp:
- Jul 23, 2019 8:20:52 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17842, comment 2
initial v1 5 5 The issue seems to affect: 6 6 * All Mac models tested. 7 * OSX ≥ 10.127 * OSX ≥ ~~10.12~~ 10.13 8 8 * Earliest !VirtualBox tested: 5.2.12 (in this ticket). 9 9 * Latest !VirtualBox tested: 6.0.10 … … 11 11 I'm going to summarize the reports just to give you an idea: 12 12 13 * 2019-02-14: '''10.12.6''', !VirtualBox 5.2.20, iMac15,1 (fth0) <<< Does '''not''' crash. 14 * 2019-07-17: '''10.11.6''', !VirtualBox 6.0.10, MacBookPro11,5 (socratis) <<< Does '''not''' crash. 15 13 16 * 2018-06-27: 10.13.5, !VirtualBox 5.2.12, MacBookPro14,3 (QA from #17842) 14 * 2019-02-14: 10.12.6, !VirtualBox 5.2.20, iMac15,1 (fth0)15 17 * 2019-02-14: 10.13.6, !VirtualBox 5.2.20, iMac15,1 (fth0) 16 18 * 2019-06-07: 10.13.6, !VirtualBox 6.0.8, MacBookPro15,1 (nyholku) … … 23 25 24 26 > ''Combining everything with an educated guess: After the accessibility zoom function has been used for the first time, GUI apps get (or do not get) some (visible or hidden) automatic menu entries (like Edit/Dictate). Every time the GUI app becomes the foreground app, the macOS menu bar is updated and the menu delegate function (QCocoaMenuDelegate in the !VirtualBox/QT case) has to handle this. The collaboration between the QCocoaMenu and NSMenu layers in QT 5.6.3 are buggy in this area (fixed multiple times in the last two years) and the QCocoaMenuDelegate is called with an already deleted menu entry when crashing. Alternatively the !VirtualBox GUI app menu code may be buggy and updating a menu entry shortly after deleting it (race condition).'' 27 28 \\ 29 30 '''EDIT''' \\ 31 Edited to reflect the fact that OSX ≥ 10.13 is required for the bug to show.
