On Thursday, 28 July 2016 at 15:24:10 UTC, bitwise wrote:
It's not about running out of memory. It's a performance issue.Example: In the following class, it would be perfectly fine, and even expected to allocate in start() but not in update(). This is because start() gets called once on object initialization, but update() would get called every frame.
Vladimir implemented counting in -profile=gc, it gives you the number of allocations and the amount allocated for each allocation point.
