{"action":"created","issue":{"url":"https://api.github.com/repos/crafatar/crafatar/issues/66","labels_url":"https://api.github.com/repos/crafatar/crafatar/issues/66/labels{/name}","comments_url":"https://api.github.com/repos/crafatar/crafatar/issues/66/comments","events_url":"https://api.github.com/repos/crafatar/crafatar/issues/66/events","html_url":"https://github.com/crafatar/crafatar/issues/66","id":53400915,"number":66,"title":"Memory issues","user":{"login":"jomo","id":3585743,"avatar_url":"https://avatars.githubusercontent.com/u/3585743?v=3","gravatar_id":"","url":"https://api.github.com/users/jomo","html_url":"https://github.com/jomo","followers_url":"https://api.github.com/users/jomo/followers","following_url":"https://api.github.com/users/jomo/following{/other_user}","gists_url":"https://api.github.com/users/jomo/gists{/gist_id}","starred_url":"https://api.github.com/users/jomo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jomo/subscriptions","organizations_url":"https://api.github.com/users/jomo/orgs","repos_url":"https://api.github.com/users/jomo/repos","events_url":"https://api.github.com/users/jomo/events{/privacy}","received_events_url":"https://api.github.com/users/jomo/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/crafatar/crafatar/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/crafatar/crafatar/labels/urgent","name":"urgent","color":"000000"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-01-05T14:27:59Z","updated_at":"2015-03-29T23:23:57Z","closed_at":null,"body":"Heroku keeps complaining about memory usage.\r\n\r\n* https://github.com/felixge/node-memory-leak-tutorial\r\n* https://hacks.mozilla.org/2012/11/tracking-down-memory-leaks-in-node-js-a-node-js-holiday-season/\r\n* https://medium.com/@Philmod/debugging-node-js-29b2097df36c\r\n* https://developer.chrome.com/devtools/docs/heap-profiling"},"comment":{"url":"https://api.github.com/repos/crafatar/crafatar/issues/comments/87495975","html_url":"https://github.com/crafatar/crafatar/issues/66#issuecomment-87495975","issue_url":"https://api.github.com/repos/crafatar/crafatar/issues/66","id":87495975,"user":{"login":"jomo","id":3585743,"avatar_url":"https://avatars.githubusercontent.com/u/3585743?v=3","gravatar_id":"","url":"https://api.github.com/users/jomo","html_url":"https://github.com/jomo","followers_url":"https://api.github.com/users/jomo/followers","following_url":"https://api.github.com/users/jomo/following{/other_user}","gists_url":"https://api.github.com/users/jomo/gists{/gist_id}","starred_url":"https://api.github.com/users/jomo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jomo/subscriptions","organizations_url":"https://api.github.com/users/jomo/orgs","repos_url":"https://api.github.com/users/jomo/repos","events_url":"https://api.github.com/users/jomo/events{/privacy}","received_events_url":"https://api.github.com/users/jomo/received_events","type":"User","site_admin":false},"created_at":"2015-03-29T23:23:57Z","updated_at":"2015-03-29T23:23:57Z","body":"Hmm, according to Douglas Crockford closures [are not](http://javascript.crockford.com/memory/leak.html) the cause of memory leaks:\r\n> Since IE is unable to do its job and reclaim the cycles, it falls on us to do it. If we explicitly break the cycles, then IE will be able to reclaim the memory. According to Microsoft, closures are the cause of memory leaks. This is of course deeply wrong, but it leads to Microsoft giving very bad advice to programmers on how to cope with Microsoft's bugs.\r\n\r\nour code definitely needs some cleanup though"}}