Closed
Bug 1453037
Opened 6 years ago
Closed 5 years ago
Crash in objc_msgSend | -[NSCandidateListViewController setAccessoryViewController:]
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox61 | --- | affected |
People
(Reporter: lizzard, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-033b8ef6-48e5-4ac7-885b-6475b0180403. ============================================================= Not sure this is the right component. There is only one crash, from a Mac, from the 20180402220122 build. Top 10 frames of crashing thread: 0 libobjc.A.dylib objc_msgSend 1 AppKit -[NSCandidateListViewController setAccessoryViewController:] 2 AppKit -[NSCandidateListTouchBarItem _didChangeCandidateListVisibility] 3 AppKit -[__NSTextInputContextAuxiliaryStorage keyboardInputSourcePopoverTouchBarItem] 4 AppKit -[NSTextInputContext _handleEvent:options:allowingSyntheticEvent:completionHandler:] 5 AppKit -[NSTextInputContext _handleEvent:allowingSyntheticEvent:] 6 AppKit -[NSView interpretKeyEvents:] 7 XUL mozilla::widget::TextInputHandler::HandleKeyDownEvent widget/cocoa/TextInputHandler.mm:1760 8 XUL -[ChildView keyDown:] widget/cocoa/nsChildView.mm:5538 9 AppKit -[NSWindow _reallySendEvent:isDelayedEvent:] =============================================================
Updated•6 years ago
|
Component: Editor → Widget: Cocoa
Comment 1•6 years ago
|
||
The input here appears to have originated from the Touchbar. My best guess at the moment is that the two crash reports in Socorro originate from someone working on adding Touchbar support to Firefox with the crash reporter enabled.
Priority: -- → P3
Comment 2•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•