A while back, we noticed an increase in crashes in our app. The crashes were marked as heap corruption, which makes them hard to debug — the location given in the stack trace (if any) can be far away in both code and time to where the problem actually lies. After a long investigation down many paths, it turned out to be an issue in Swift itself. After sharing a few tweets about it on Twitter, I ha
![Solving a Mysterious Heap Corruption Crash](https://cdn-ak-scissors.b.st-hatena.com/image/square/487d79671002563e8263efdcf56d32a842bc3ae0/height=288;version=1;width=512/https%3A%2F%2Ftopologyeyewear.github.io%2Fengineering-blog%2Fassets%2Ftopology_bg.png)