Closed solo999 closed 10 years ago
solo999
commented
10 years ago Update:
nothing wrong with zones. the problem was in svg.js, which continuously fire fx.render but because of zones installed, the loop become expensive and Crome raised CPU usage...
And it is good I had zones installed, which gave me CPU 100% loading to catch the actual problem
arunoda
commented
10 years ago Zones create a new error object in order to get the stack. This does lot of places where we don't need to.
I will do some optimizations on this too.
On Monday, July 14, 2014, solo999 notifications@github.com wrote:
Closed #7 https://github.com/meteorhacks/meteor-zone/issues/7.
— Reply to this email directly or view it on GitHub https://github.com/meteorhacks/meteor-zone/issues/7#event-141261327.
Arunoda Susiripala I curate Meteor Weekly - Check it out! http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly
arunoda
commented
10 years ago We've make some improvements to zones package to not to create zones on animation frames.
What in zones.js can cause Chrome continuously process animation frames and pump CPU load to 100%?
It happened to me only when I edit drawn object in Leaflet Draw and save it. CPU load jump immediately from 15% to 90+% and timeline in Dev Tools shows continuos animation frames request in zones.js
After removing meteor-zone package all become normal: CPU load is less than 10% under the same conditions as above.
Mac OS 10.9.4, Chrome 35, Meteor 0.8.2