Re: Crash with "illegal opcode" - how to debug this issue?
No other response so far…toggle quoted messageShow quoted text
That particular crash is just one example. There are numerous crash reports with the same basic crash, but not always in a CATransaction callback, though that is a very common one.
Perhaps it’s simply a memory issue with something freed prematurely. It’s the most straightforward explanation, if not the most straightforward thing to track down. I’ll proceed on that basis - it’s just that such bugs don’t usually show up in this form.
On 26 May 2018, at 4:37 am, Jack Brindle <firstname.lastname@example.org> wrote: