Open Bug 1884624 Opened 3 months ago Updated 4 days ago

[macOS 14] Crash in [@ __CFCheckCFInfoPACSignature] on 124 branch

Categories

(Core :: Widget: Cocoa, defect, P3)

Product:
Core
Component:
Widget: Cocoa
Platform:
ARM64
macOS
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox125 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/501c92b7-6cc5-45a7-8231-d8ee40240307

Reason: EXC_BREAKPOINT / EXC_ARM_BREAKPOINT

Top 10 frames of crashing thread:

0  CoreFoundation  __CFCheckCFInfoPACSignature  
1  CoreFoundation  CFRunLoopObserverInvalidate  
2  AppKit  -[NSWindow _cancelPerformSelectors]  
3  AppKit  -[NSWindow dealloc]  
4  XUL  -[BaseWindow dealloc]  widget/cocoa/nsCocoaWindow.mm:3571
5  XUL  -[ToolbarWindow dealloc]  widget/cocoa/nsCocoaWindow.mm:4085
6  Foundation  _NSKVOPerformWithDeallocatingObservable  
7  Foundation  NSKVODeallocate  
8  libdispatch.dylib  _dispatch_client_callout  
9  libdispatch.dylib  _dispatch_main_queue_drain

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2024-02-02
  • Process type: Parent
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: No

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Widget: Cocoa
Severity: -- → S3
Priority: -- → P3

These crashes are all on macOS 14 -- so ultimately they're (probably) caused by one or more macOS bugs. But they're much more likely to happen on the Mozilla 124 branch and up -- so something must have changed in Mozilla code to make them more likely.

"KVO" stands for "key-value observing" -- for observing when a value changes without having to use delegates. This feature has been around for a while -- it's not new in macOS 14. And as best I can tell Mozilla code doesn't use it directly.

Another bug (unfortunately security sensitive) is also macOS 14 only and much more frequent on the 124 branch and up. So the two may be related.

https://crash-stats.mozilla.org/search/?proto_signature=~__CFCheckCFInfoPACSignature&platform=Mac%20OS%20X&date=%3E%3D2024-03-11T16%3A03%3A00.000Z&date=%3C2024-03-25T16%3A03%3A00.000Z&_facets=signature&_facets=platform_version&_facets=cpu_arch&_facets=proto_signature&_facets=version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-platform_version

Summary: Crash in [@ __CFCheckCFInfoPACSignature] → [macOS 14] Crash in [@ __CFCheckCFInfoPACSignature] on 124 branch and up

And as best I can tell Mozilla code doesn't use it directly.

Not true. Search at searchfox.org on "addObserver:".

Crash Signature: [@ __CFCheckCFInfoPACSignature] → [@ __CFCheckCFInfoPACSignature] [@ _CFAssertMismatchedTypeID ]

There are almost none of these on the 125 branch (currently in beta) and up. But let's see if that persists after the FF 125 release. Edit: Yes, it has.

Summary: [macOS 14] Crash in [@ __CFCheckCFInfoPACSignature] on 124 branch and up → [macOS 14] Crash in [@ __CFCheckCFInfoPACSignature] on 124 branch

trying to add more CI to macosx 14.x I run into this crash often:
https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=3d26f0f3e31d4c8cbb1b3268b71c60d792fa317f

this is on the m2 chipset (aarch64). It could be something I need to adjust in the build, test harness, toolchains, os setup, etc.

Given this is the same machine setup and build we run perf tests on for macosx 14.x, I would assume things are for the most part setup correctly.

You need to log in before you can comment on or make changes to this bug.