Crash in [@ nsMenuBarX::Paint] with NSInvalidArgumentException: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | wontfix |
firefox-esr115 | --- | wontfix |
firefox86 | --- | unaffected |
firefox87 | --- | wontfix |
firefox88 | --- | wontfix |
firefox89 | --- | wontfix |
firefox97 | --- | wontfix |
firefox98 | --- | wontfix |
firefox99 | --- | wontfix |
firefox100 | --- | wontfix |
firefox101 | --- | wontfix |
firefox102 | --- | wontfix |
firefox103 | --- | wontfix |
firefox104 | --- | wontfix |
firefox120 | --- | wontfix |
firefox121 | --- | wontfix |
firefox122 | --- | fixed |
People
(Reporter: mstange, Assigned: spohl)
References
(Regression)
Details
(Keywords: crash, regression, Whiteboard: [mac:stability])
Crash Data
Attachments
(2 files)
Crash report: https://crash-stats.mozilla.org/report/index/c8049cd0-e2c0-4e47-8f2a-526140210319
MOZ_CRASH Reason: MOZ_CRASH(Encountered unexpected Objective C exception)
Obj-C Exception data:
NSInvalidArgumentException: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
Thrown at stack:
__exceptionPreprocess (in CoreFoundation) + 0x93
objc_exception_throw (in libobjc.A.dylib) + 0x30
_CFThrowFormattedException (in CoreFoundation) + 0xc2
-[__NSArrayM insertObject:atIndex:] (in CoreFoundation) + 0x4dd
-[NSMenu insertItem:atIndex:] (in AppKit) + 0x12e
nsMenuBarX::Paint() (in XUL) + 0x6f
Top 10 frames of crashing thread:
0 XUL nsMenuBarX::Paint widget/cocoa/nsMenuBarX.mm:459
1 XUL nsMenuBarX::Create widget/cocoa/nsMenuBarX.mm:148
2 XUL mozilla::widget::NativeMenuSupport::CreateNativeMenuBar widget/cocoa/NativeMenuSupport.mm:18
3 XUL mozilla::LoadNativeMenus xpfe/appshell/AppWindow.cpp:3006
4 XUL mozilla::dom:: dom/promise/Promise.cpp:384
5 XUL mozilla::dom::NativeHandlerCallback dom/promise/Promise.cpp:337
6 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:520
7 XUL mozilla::dom::CallbackObject::CallSetup::~CallSetup dom/bindings/CallbackObject.cpp:342
8 XUL js::Call js/src/vm/Interpreter.cpp:597
9 XUL PromiseReactionJob js/src/builtin/Promise.cpp:1905
Comment 1•4 years ago
|
||
Set release status flags based on info from the regressing bug 1692647
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
P2 for over a year doesn't seem to reflect reality and there is no-one assigned. I'm going to reset this.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
bugherder |
Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 8•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
:spohl do you still plan on working on this?
Assignee | ||
Comment 10•2 years ago
|
||
I happen to be looking at an issue that deals with menu items in bug 1642138 and I'll keep this bug in mind.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 5 desktop browser crashes on Mac on beta (startup)
:spohl, could you consider increasing the severity of this top-crash bug?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit auto_nag documentation.
Comment 13•1 year ago
|
||
Updated•1 year ago
|
Comment 14•1 year ago
|
||
bugherder |
Comment 15•1 year ago
|
||
The patch landed in nightly and beta is affected.
:spohl, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval. Also, don't forget to request an uplift for the patches in the regression caused by this fix.
- If no, please set
status-firefox121
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 16•1 year ago
|
||
(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #15)
The patch landed in nightly and beta is affected.
:spohl, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval. Also, don't forget to request an uplift for the patches in the regression caused by this fix.
- If no, please set
status-firefox121
towontfix
.For more information, please visit BugBot documentation.
Since this is a longstanding issue and that the patch here has caused regressions before, it does not seem prudent to uplift it at this time. Setting status-firefox121
to wontfix
.
Updated•1 year ago
|
Description
•