3 ms·
It's a lot more rare problem compared to not correctly freeing memory though. And it's not hard to fix.
by speedgoose 5y ago
It's a lot more rare problem compared to not correctly freeing memory though. And it's not hard to fix.
- vlovich123 5y agoMy point was that a GC’ed language doesn’t guarantee that this particular instance has to do with anything, especially since they use Swift for a lot of code (which does a form of GC via reference counting). The recommendation to switch to a tracing GC’ed language is naive because there are better solutions to this problem that don’t require a GC (ARC from Apple, managed pointers in c++, rust lifetime ownership etc), solve 90% of the problems with far less cost, which matters for mobile battery powered devices but also matters in high performance servers)