On 6 Nov 2014, at 23:40, Graham Cox wrote:
Looks like an object is not removing itself as an observer of window
notifications prior to deallocation […]
The crash happens when I re-use the window with the WebView, i.e. no
(major) objects are released.
The crash (almost) disappeared when I st
Looks like an object is not removing itself as an observer of window
notifications prior to deallocation. The notification center holds on to weak
references, so these can become stale if not purposely removed, usually by a
call to -removeObserver: as part of the -dealloc method (with ARC you wo
On 30 Oct 2014, at 17:26, Fritz Anderson wrote:
I haven’t encountered this myself. This is stream-of-consciousness,
adding the presence of convertRect:toView: in the trace as the
immediate caller…
Thanks for your thoughts on the issue.
I haven’t pinpointed the exact cause of the crash, but I
I haven’t encountered this myself. This is stream-of-consciousness, adding the
presence of convertRect:toView: in the trace as the immediate caller…
…
The classic cause of a message arriving at the wrong object is that the
expected object had been deallocated and its address recycled for the ob
Since Yosemite I have seen a lot of crash reports submitted where the
crash is triggered by closing a window and it mostly ends with sending
`isFlipped`, `_isLayerBacked`, or `transformRect:` to a wrong object.
I have attached a sample crash report below.
Does anyone else see this? Anyone know