Why Nostr? What is Njump?
2023-10-09 16:43:29
in reply to

Matt Massicotte on Nostr: npub1kvt2w…u0vtn Yes, so first this is not running a fetch result, it is ...

Yes, so first this is not running a fetch result, it is *deallocating* one. What you are seeing here is a classic overrelease effect. There could be more than one, unfortunately, that's the nature of heap corruption. You want the *cause*, which can be pretty separated in time. But I bet it is related to your core data models somehow.

You are right that dangling pointers are really unusual in Swift. But, regardless, start checking out zombies!
Author Public Key
npub1xfkfzq9r68c7e5xnt0u4jzexx0nvy239m6as32k8n4d0jqaaseeqskwjhv