{"action":"opened","issue":{"url":"https://api.github.com/repos/dtoubelis/sails-cassandra/issues/21","labels_url":"https://api.github.com/repos/dtoubelis/sails-cassandra/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/dtoubelis/sails-cassandra/issues/21/comments","events_url":"https://api.github.com/repos/dtoubelis/sails-cassandra/issues/21/events","html_url":"https://github.com/dtoubelis/sails-cassandra/issues/21","id":72351259,"number":21,"title":"Possible memory leak","user":{"login":"BrighTide","id":2033608,"avatar_url":"https://avatars.githubusercontent.com/u/2033608?v=3","gravatar_id":"","url":"https://api.github.com/users/BrighTide","html_url":"https://github.com/BrighTide","followers_url":"https://api.github.com/users/BrighTide/followers","following_url":"https://api.github.com/users/BrighTide/following{/other_user}","gists_url":"https://api.github.com/users/BrighTide/gists{/gist_id}","starred_url":"https://api.github.com/users/BrighTide/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BrighTide/subscriptions","organizations_url":"https://api.github.com/users/BrighTide/orgs","repos_url":"https://api.github.com/users/BrighTide/repos","events_url":"https://api.github.com/users/BrighTide/events{/privacy}","received_events_url":"https://api.github.com/users/BrighTide/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-01T04:25:38Z","updated_at":"2015-05-01T04:25:38Z","closed_at":null,"body":"When inserting a large volume of entries like so:\r\n        function insert(){\r\n                inserted++;\r\n                Model.create({id:inserted}).exec(insert);\r\n        }        \r\n        insert();\r\n\r\n, the memory the process uses increases slowly, until it caps out at around 1.4gb and the whole thing slows to a crawl. If you stop the loop above at any point the process just chills with the memory it's gained without giving anything back, this doesn't appear to happen with any other adapter. I've tried doing some mem profiling, but for whatever reason the node-inspector on windows starts running around with it's hair on fire when you try to do a recording. The heap snapshots suggested that the records I'm inserting might be getting stored somewhere in the process, but I couldn't find anything in fly by of the code. Using node 0.12 on windows through the latest versions of the adapter and sails."}}