394558 - crash [@ objc_msgSend] [@ AppKitMenuEventHandler]

Status: RESOLVED INCOMPLETE

(Core :: Widget: Cocoa, defect)

Description

[Mats Palmgren (inactive)]

Note sure exactly what I did to crash it, I think it was something like this:
1. Move the mouse over the menubar/menus
2. with a submenu open, type ESC and then CMD+Q rapidly

It wasn't reproducible.
Just before the crash I got this assertion:

###!!! ASSERTION: lazy state set with no XUL content builder in ancestor chain: 'Error', file /Users/mats/firefox/mozilla/content/xul/content/src/nsXULElement.cpp, line 1612

Thread 0 Crashed:
0   libobjc.A.dylib       	0x90a59380 objc_msgSend + 16
1   com.apple.AppKit      	0x933630d7 AppKitMenuEventHandler + 2334
2   com.apple.HIToolbox   	0x92de1537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
3   com.apple.HIToolbox   	0x92de0bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
4   com.apple.HIToolbox   	0x92de0aa1 SendEventToEventTargetWithOptions + 55
5   com.apple.HIToolbox   	0x92e84bc7 SendMenuPopulate(MenuData*, OpaqueEventTargetRef*, unsigned long, double) + 259
6   com.apple.HIToolbox   	0x92e9fec2 PopulateMenu(MenuData*, OpaqueEventTargetRef*, CheckMenuData*, unsigned long, double) + 34
7   com.apple.HIToolbox   	0x92e9f591 Check1MenuForKeyEvent(MenuData*, CheckMenuData*) + 147
8   com.apple.HIToolbox   	0x92e9ef9e CheckMenusForKeyEvent(MenuData*, CheckMenuData*) + 638
9   com.apple.HIToolbox   	0x92e9ecc4 IsMenuKeyEvent(MenuData*, OpaqueEventRef*, unsigned long, MenuData**, unsigned short*) + 630
10  com.apple.HIToolbox   	0x92e9ea0d IsMenuKeyEvent + 109
11  com.apple.AppKit      	0x93362608 _NSGetMenuItemForCommandKeyEvent + 420
12  com.apple.AppKit      	0x93354ead _NSHandleCarbonMenuEvent + 628
13  com.apple.AppKit      	0x932887fc _DPSNextEvent + 1491

Comment 1

[Mats Palmgren (inactive)]

Attachment: crash data

Comment 2

[Jesse Ruderman]

Steven, can you determine whether the stack trace and steps here are useful?  If not, please mark this bug as incomplete.

Comment 3

[Steven Michaud [:smichaud] (Retired)]

There isn't much information in the stack trace.  And I find (at
http://crash-stats.mozilla.com) exactly one instance of the same crash
over the last four weeks, in an equally old FF build:

http://crash-stats.mozilla.com/report/index/1d27cb45-8747-4584-840b-25eed2090816

There isn't enough to work with here, nor any evidence that the
problem is urgent.  So marking incomplete.