{"action":"opened","issue":{"url":"https://api.github.com/repos/HackedByChinese/ng-idle/issues/140","repository_url":"https://api.github.com/repos/HackedByChinese/ng-idle","labels_url":"https://api.github.com/repos/HackedByChinese/ng-idle/issues/140/labels{/name}","comments_url":"https://api.github.com/repos/HackedByChinese/ng-idle/issues/140/comments","events_url":"https://api.github.com/repos/HackedByChinese/ng-idle/issues/140/events","html_url":"https://github.com/HackedByChinese/ng-idle/issues/140","id":134845948,"number":140,"title":"Performance - too many digest cycles triggered","user":{"login":"webartoli","id":11707475,"avatar_url":"https://avatars.githubusercontent.com/u/11707475?v=3","gravatar_id":"","url":"https://api.github.com/users/webartoli","html_url":"https://github.com/webartoli","followers_url":"https://api.github.com/users/webartoli/followers","following_url":"https://api.github.com/users/webartoli/following{/other_user}","gists_url":"https://api.github.com/users/webartoli/gists{/gist_id}","starred_url":"https://api.github.com/users/webartoli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webartoli/subscriptions","organizations_url":"https://api.github.com/users/webartoli/orgs","repos_url":"https://api.github.com/users/webartoli/repos","events_url":"https://api.github.com/users/webartoli/events{/privacy}","received_events_url":"https://api.github.com/users/webartoli/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-19T11:46:53Z","updated_at":"2016-02-19T11:46:53Z","closed_at":null,"body":"It seems that for some reason ng-idle is triggering too many AngularJS `digest` cycles.\r\nThis cause performance issues on big applications, especially when a lot of non trivial AngularJS filters are used (filters are evaluated at every digest cycle).\r\n\r\n\r\n**repro:**\r\n- open the ng-idle demo website (http://hackedbychinese.github.io/ng-idle/)\r\n- start the demo\r\n- quickly move the mouse around for 2-3 seconds\r\n\r\nThe browser cpu usage goes up (5% on a Intel i7 pc, much more on less powerful machines).\r\n\r\nMoving the mouse without starting the demo doesn't cause any significant CPU usage."}}