{"action":"opened","issue":{"url":"https://api.github.com/repos/phstc/shoryuken/issues/118","labels_url":"https://api.github.com/repos/phstc/shoryuken/issues/118/labels{/name}","comments_url":"https://api.github.com/repos/phstc/shoryuken/issues/118/comments","events_url":"https://api.github.com/repos/phstc/shoryuken/issues/118/events","html_url":"https://github.com/phstc/shoryuken/issues/118","id":95757813,"number":118,"title":"Shoryuken Hangs","user":{"login":"brianp","id":179134,"avatar_url":"https://avatars.githubusercontent.com/u/179134?v=3","gravatar_id":"","url":"https://api.github.com/users/brianp","html_url":"https://github.com/brianp","followers_url":"https://api.github.com/users/brianp/followers","following_url":"https://api.github.com/users/brianp/following{/other_user}","gists_url":"https://api.github.com/users/brianp/gists{/gist_id}","starred_url":"https://api.github.com/users/brianp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brianp/subscriptions","organizations_url":"https://api.github.com/users/brianp/orgs","repos_url":"https://api.github.com/users/brianp/repos","events_url":"https://api.github.com/users/brianp/events{/privacy}","received_events_url":"https://api.github.com/users/brianp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-17T22:34:05Z","updated_at":"2015-07-17T22:34:05Z","closed_at":null,"body":"Hey,\r\n\r\nI wasn't going to create an issue but I noticed this was an issue previously and the fix was to version lock celluloid at 0.15.2 (https://github.com/phstc/shoryuken/pull/11/files).\r\n\r\nIf there is a discussion group that may be a better place then the issue tracker.\r\n\r\nRunning:\r\nruby 2.1.5p273 (2014-11-13 revision 48405)\r\nshoryuken (~> 1.0.2)\r\ncelluloid (0.16.0)\r\n\r\nThe Shoryuken process starts up fine. After about 30 minutes the process begins to hang. After about 50 minutes the process may die but is certainly no longer polling for messages.\r\n\r\nAfter the process dies, if I try to restart the process manually (un-daemonized) with or without -v it simply hangs with no output.\r\n\r\nI tracked memory usage and didn't notice any abnormalities.\r\n\r\nAny specific debugging steps I can go through?\r\n\r\nCheers,"}}