{"action":"created","issue":{"url":"https://api.github.com/repos/sequelize/sequelize/issues/2632","labels_url":"https://api.github.com/repos/sequelize/sequelize/issues/2632/labels{/name}","comments_url":"https://api.github.com/repos/sequelize/sequelize/issues/2632/comments","events_url":"https://api.github.com/repos/sequelize/sequelize/issues/2632/events","html_url":"https://github.com/sequelize/sequelize/issues/2632","id":50361720,"number":2632,"title":"Sequelize + Postgres: 100% CPU usage, memory sky rocketing","user":{"login":"kytwb","id":412895,"avatar_url":"https://avatars.githubusercontent.com/u/412895?v=3","gravatar_id":"","url":"https://api.github.com/users/kytwb","html_url":"https://github.com/kytwb","followers_url":"https://api.github.com/users/kytwb/followers","following_url":"https://api.github.com/users/kytwb/following{/other_user}","gists_url":"https://api.github.com/users/kytwb/gists{/gist_id}","starred_url":"https://api.github.com/users/kytwb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kytwb/subscriptions","organizations_url":"https://api.github.com/users/kytwb/orgs","repos_url":"https://api.github.com/users/kytwb/repos","events_url":"https://api.github.com/users/kytwb/events{/privacy}","received_events_url":"https://api.github.com/users/kytwb/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/sequelize/sequelize/labels/bug","name":"bug","color":"d7e102"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2014-11-28T10:42:49Z","updated_at":"2015-01-12T15:50:08Z","closed_at":"2015-01-11T09:04:32Z","body":"Just a quick report on something I experienced many times. Using `includes` to fetch associations, my nodejs process goes wild, taking 100% of CPU and using all the memory available. It's hard to reproduce in local as it has something to deal with my database set state on my staging server.\r\nI'll be back in a bit with more info. I hope. Meanwhile, here the piece of code leading to the issue. Everything's fine before the `return`'s line, then the bug happens and promise never resolves anything (server crashes). It had happened by the past on other sequelize queries.\r\n\r\n```javascript\r\nreturn api.models.prospect.findAll({\r\n    where: {\r\n        merchantId: '1'\r\n    }, includes: {\r\n        all: true,\r\n        nested: false\r\n    }\r\n}).then(function (result) {\r\n    connection.response = result;\r\n});\r\n```\r\n\r\nNobody every experienced / reported anything like this?"},"comment":{"url":"https://api.github.com/repos/sequelize/sequelize/issues/comments/69590357","html_url":"https://github.com/sequelize/sequelize/issues/2632#issuecomment-69590357","issue_url":"https://api.github.com/repos/sequelize/sequelize/issues/2632","id":69590357,"user":{"login":"kytwb","id":412895,"avatar_url":"https://avatars.githubusercontent.com/u/412895?v=3","gravatar_id":"","url":"https://api.github.com/users/kytwb","html_url":"https://github.com/kytwb","followers_url":"https://api.github.com/users/kytwb/followers","following_url":"https://api.github.com/users/kytwb/following{/other_user}","gists_url":"https://api.github.com/users/kytwb/gists{/gist_id}","starred_url":"https://api.github.com/users/kytwb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kytwb/subscriptions","organizations_url":"https://api.github.com/users/kytwb/orgs","repos_url":"https://api.github.com/users/kytwb/repos","events_url":"https://api.github.com/users/kytwb/events{/privacy}","received_events_url":"https://api.github.com/users/kytwb/received_events","type":"User","site_admin":false},"created_at":"2015-01-12T15:50:08Z","updated_at":"2015-01-12T15:50:08Z","body":"@mickhansen not slow, just indefinitly hanging (been waiting for 20/30mn, dataset isn't big at all)."}}