{"action":"closed","issue":{"url":"https://api.github.com/repos/aaronkennedy/ZingElements/issues/247","repository_url":"https://api.github.com/repos/aaronkennedy/ZingElements","labels_url":"https://api.github.com/repos/aaronkennedy/ZingElements/issues/247/labels{/name}","comments_url":"https://api.github.com/repos/aaronkennedy/ZingElements/issues/247/comments","events_url":"https://api.github.com/repos/aaronkennedy/ZingElements/issues/247/events","html_url":"https://github.com/aaronkennedy/ZingElements/issues/247","id":52939043,"number":247,"title":"Non-reponsive Simulator Agents consuming 100% CPU","user":{"login":"michaelahokas","id":8209164,"avatar_url":"https://avatars.githubusercontent.com/u/8209164?v=3","gravatar_id":"","url":"https://api.github.com/users/michaelahokas","html_url":"https://github.com/michaelahokas","followers_url":"https://api.github.com/users/michaelahokas/followers","following_url":"https://api.github.com/users/michaelahokas/following{/other_user}","gists_url":"https://api.github.com/users/michaelahokas/gists{/gist_id}","starred_url":"https://api.github.com/users/michaelahokas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michaelahokas/subscriptions","organizations_url":"https://api.github.com/users/michaelahokas/orgs","repos_url":"https://api.github.com/users/michaelahokas/repos","events_url":"https://api.github.com/users/michaelahokas/events{/privacy}","received_events_url":"https://api.github.com/users/michaelahokas/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/aaronkennedy/ZingElements/labels/bug","name":"bug","color":"fc2929"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2014-12-26T21:05:53Z","updated_at":"2016-02-28T15:52:15Z","closed_at":"2016-02-28T15:52:15Z","body":"![screen shot 2014-12-26 at 17 32 35](https://cloud.githubusercontent.com/assets/8209164/5559379/03d3ca6e-8d9f-11e4-83b8-089d48f96133.png)\r\n\r\nI ended up with a quite a lot of simulator agents that were not responsive. Each one was consuming close to 100% CPU."}}