Upgrade zone.js => WAS: Heavy CPU usage over time with Zone and requestAnimationFrame

[justindujardin]

I have a "game" that manages its own time loop using requestAnimationFrame. I have ported it to angular2, and it works really well except that I experience pretty severely degraded performance over time. When I capture CPU profiles Zone ends up replacing the idle time that was there when the page loaded.

I'm not sure what to make of it, but it's very easy to reproduce--just open the page and take a profile, then wait a minute and take another profile.

Example: http://justindujardin.github.io/angular2-rpg

[PatrickJS]

you can run it outside of zone.js

NgZone#runOutsideAngular(() => {
  requestAnimationFrame(() => console.log());
})

[justindujardin]

@gdi2290 that's an interesting idea, but it would exclude my app from change-detection then, yes?

The reason I filed this issue is because my renderer was very stable in 1.x, but in 2.0 it degrades very quickly, which suggests to me some kind of resource leak in Zone. I notice a large amount of time being spent on what appears to be patching get/set properties.

[justindujardin]

I dug into this a little bit, and it appears that the requestAnimationFrame wrapper in zone.js is flawed.

I filed an issue over there: angular/zone.js#143

[mhevery]

Should be assigned to @btford

[jomeier]

@mhevery @btford Any news on this one? I also try to use RequestAnimationFrame with Angular 2 and suffer from huge performance drops.

[mhevery]

I thought this was resolved. Can you verify?