Same for Javascript, at least when aiming for perfect 60FPS, the only good garbage collection is the one that doesn&#x27;t occur after init, and maybe when switching maps or whatnot. Even the 0.09ms in the article is way too much and means a skipped frame. Maybe a way to think of it is to treat GC like optional automatic destructors, which should get called (more or less) when <i>you</i> want them to, not as something you just &quot;don&#x27;t have to think about&quot; (if you run something in a loop and need it to be silk smooth, that is).<p>Incidentally, this is great: <a href="https:&#x2F;&#x2F;www.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;46.0beta&#x2F;releasenotes&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;46.0beta&#x2F;releasenotes&#x2F;</a><p>&gt; Allocation and garbage collection pause profiling in the performance panel