{"action":"opened","issue":{"url":"https://api.github.com/repos/strongloop/loopback/issues/1084","labels_url":"https://api.github.com/repos/strongloop/loopback/issues/1084/labels{/name}","comments_url":"https://api.github.com/repos/strongloop/loopback/issues/1084/comments","events_url":"https://api.github.com/repos/strongloop/loopback/issues/1084/events","html_url":"https://github.com/strongloop/loopback/issues/1084","id":57145118,"number":1084,"title":"Create benchmarks & fail on leaks","user":{"login":"STRML","id":1197375,"avatar_url":"https://avatars.githubusercontent.com/u/1197375?v=3","gravatar_id":"","url":"https://api.github.com/users/STRML","html_url":"https://github.com/STRML","followers_url":"https://api.github.com/users/STRML/followers","following_url":"https://api.github.com/users/STRML/following{/other_user}","gists_url":"https://api.github.com/users/STRML/gists{/gist_id}","starred_url":"https://api.github.com/users/STRML/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/STRML/subscriptions","organizations_url":"https://api.github.com/users/STRML/orgs","repos_url":"https://api.github.com/users/STRML/repos","events_url":"https://api.github.com/users/STRML/events{/privacy}","received_events_url":"https://api.github.com/users/STRML/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-10T08:37:48Z","updated_at":"2015-02-10T08:37:48Z","closed_at":null,"body":"Continuation of [this discussion](https://github.com/strongloop/loopback/pull/1083#issuecomment-73628853) on the critical leak that affected `2.8.7` to `2.12.1`.\r\n\r\nWe need a way to detect if something like this happens again. \r\n\r\nIt would be a good idea IMO to have general benchmarks in any case, so we can detect how our changes affect loopback's throughput. We could also fail the benchmark outright if a `leak` event is caught by [node-memwatch](https://github.com/lloyd/node-memwatch)."}}