3 ms·
The autorelease optimization actually regularly breaks, because not even the compiler engineers remember it exists, and it relies on libraries tall-calling -aut
by astrange 7y ago
The autorelease optimization actually regularly breaks, because not even the compiler engineers remember it exists, and it relies on libraries tall-calling -autorelease which they also forget to do.
Even without it, there isn't a pausing problem because you can clear the pool at the end of the runloop tick, when the app is idle anyway.
- inlined 7y agoBut if you didn’t had the trick, CPU intensive runloop ticks could create lots of small objects that were put in the pool because they had a 0 refcount as a function returned the value. That’s why we had the ability to write our own pools.