{"action":"created","issue":{"url":"https://api.github.com/repos/SickRage/SickRage/issues/2450","repository_url":"https://api.github.com/repos/SickRage/SickRage","labels_url":"https://api.github.com/repos/SickRage/SickRage/issues/2450/labels{/name}","comments_url":"https://api.github.com/repos/SickRage/SickRage/issues/2450/comments","events_url":"https://api.github.com/repos/SickRage/SickRage/issues/2450/events","html_url":"https://github.com/SickRage/SickRage/issues/2450","id":181858125,"number":2450,"title":"High constant memory usage on Synology","user":{"login":"nicke736","id":22694249,"avatar_url":"https://avatars.githubusercontent.com/u/22694249?v=3","gravatar_id":"","url":"https://api.github.com/users/nicke736","html_url":"https://github.com/nicke736","followers_url":"https://api.github.com/users/nicke736/followers","following_url":"https://api.github.com/users/nicke736/following{/other_user}","gists_url":"https://api.github.com/users/nicke736/gists{/gist_id}","starred_url":"https://api.github.com/users/nicke736/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nicke736/subscriptions","organizations_url":"https://api.github.com/users/nicke736/orgs","repos_url":"https://api.github.com/users/nicke736/repos","events_url":"https://api.github.com/users/nicke736/events{/privacy}","received_events_url":"https://api.github.com/users/nicke736/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-09T01:25:08Z","updated_at":"2016-10-09T01:25:09Z","closed_at":null,"body":"I using Synology Diskstation DS2413+ with upgraded memory to 2048MB.\r\n\r\nBranch/Commit: Master\r\nOS: Linux-3.10.77-x86_64-with-glibc2.2.5\r\nDSM version: DSM 6.0.2-8451 Update 1\r\nWhat you did: Reinstalled sickbeard-custom servral times with new configurations and checked them so they are correct.\r\nWhat happened: After all shows (18) is added in sickrage memory usage on the Synology stucks on 90-92% and never goes down (2 days and no dropping).\r\nWhat you expected: I expecting memory usage to be low then searches and processing are inactive. There also no active warnings or errors in the log.\r\nLogs: Attached file, I have censored the apikey with ****.\r\n[Sickrage Debug Log.txt](https://github.com/SickRage/SickRage/files/518039/Sickrage.Debug.Log.txt)\r\n \r\n"},"comment":{"url":"https://api.github.com/repos/SickRage/SickRage/issues/comments/252458067","html_url":"https://github.com/SickRage/SickRage/issues/2450#issuecomment-252458067","issue_url":"https://api.github.com/repos/SickRage/SickRage/issues/2450","id":252458067,"user":{"login":"SickRage2","id":15840237,"avatar_url":"https://avatars.githubusercontent.com/u/15840237?v=3","gravatar_id":"","url":"https://api.github.com/users/SickRage2","html_url":"https://github.com/SickRage2","followers_url":"https://api.github.com/users/SickRage2/followers","following_url":"https://api.github.com/users/SickRage2/following{/other_user}","gists_url":"https://api.github.com/users/SickRage2/gists{/gist_id}","starred_url":"https://api.github.com/users/SickRage2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SickRage2/subscriptions","organizations_url":"https://api.github.com/users/SickRage2/orgs","repos_url":"https://api.github.com/users/SickRage2/repos","events_url":"https://api.github.com/users/SickRage2/events{/privacy}","received_events_url":"https://api.github.com/users/SickRage2/received_events","type":"User","site_admin":false},"created_at":"2016-10-09T01:25:09Z","updated_at":"2016-10-09T01:25:09Z","body":"Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked\n\n- [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected\n- [ ] Enable debug logging (be sure to disable after the bug is fixed)\n- [ ] Post debug logs, either inline (for smaller logs) or using gist\n\nPlease make sure you also read [how to create an issue](https://github.com/SickRage/sickrage-issues/blob/master/README.md) and followed all of the steps. \n\nThe title should describe your issue. Having \"SR not working\" or \"I get this bug\" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.\n\nSometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.\n\nThanks!"}}
{"actor":{"display_login":"SickRage2"}}