Bugzilla

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on a deleted `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on a `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on a `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`). *Very* wierd.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on a `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`). *Very* wierd.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on an `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`). *Very* wierd.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on an `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`, `r10`). *Very* wierd.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on an `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. I need to puzzle out the machine code for `objc_msgSend` to figure out what's happening.

As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`, `r10`). *Very* wierd.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory.

Or maybe there's some kind of heap corruption.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on an `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`, `r10`, in `objc_msgSend()`). *Very* weird.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory. (Checking further, in `-[NSView _finalize]` and `objc_destroyWeak()`, I don't see this.)

Or maybe there's some kind of heap corruption.

I suspect we should just let Apple do its thing here.

For what it's worth, these crashes happen when `-[NSView(NSTrackingArea) trackingAreas]` is called on an `NSView` object. I found this out by looking at the AppKit framework's `-[_NSTrackingAreaAKManager _updateActiveTrackingAreasForWindowLocation:modifierFlags:]` in a disassembler.

The `NSView` object itself has *not* been deleted. As best I can tell it's the `NSView` object's *class* that's been deleted (`self->isa`, `r10` in `objc_msgSend()`). *Very* weird.

Or maybe the `NSView` object is in the process of being deleted, such that its `self->isa` pointer points to deleted memory. (Checking further, in `-[NSView _finalize]` and `objc_destroyWeak()`, I don't see this.)

Or maybe there's some kind of heap corruption.

I suspect we should just let Apple do its thing here.