{"action":"created","issue":{"url":"https://api.github.com/repos/i3/i3lock/issues/46","repository_url":"https://api.github.com/repos/i3/i3lock","labels_url":"https://api.github.com/repos/i3/i3lock/issues/46/labels{/name}","comments_url":"https://api.github.com/repos/i3/i3lock/issues/46/comments","events_url":"https://api.github.com/repos/i3/i3lock/issues/46/events","html_url":"https://github.com/i3/i3lock/issues/46","id":120144493,"number":46,"title":"i3lock raise_loop process does not exit","user":{"login":"tcatm","id":345092,"avatar_url":"https://avatars.githubusercontent.com/u/345092?v=3","gravatar_id":"","url":"https://api.github.com/users/tcatm","html_url":"https://github.com/tcatm","followers_url":"https://api.github.com/users/tcatm/followers","following_url":"https://api.github.com/users/tcatm/following{/other_user}","gists_url":"https://api.github.com/users/tcatm/gists{/gist_id}","starred_url":"https://api.github.com/users/tcatm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tcatm/subscriptions","organizations_url":"https://api.github.com/users/tcatm/orgs","repos_url":"https://api.github.com/users/tcatm/repos","events_url":"https://api.github.com/users/tcatm/events{/privacy}","received_events_url":"https://api.github.com/users/tcatm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-12-03T10:55:42Z","updated_at":"2016-05-14T11:06:44Z","closed_at":null,"body":"In `raise_loop` i3lock is waiting for events on its window. On a few occasions this has caused i3lock to not exit on my system after unlocking. At best, this causes stray processes and at worst it prevents locking the screen when external scripts check whether the previous i3lock run terminated.\r\n\r\nBy analysing the running i3lock process using gdb I have found the window it is waiting for doesn't exist anymore (Obvisouly, this is expected as my session is unlocked). I'm going to run i3lock with `--debug` from now on so I get a better idea of what's going on.\r\n\r\nI can't reproduce this yet."},"comment":{"url":"https://api.github.com/repos/i3/i3lock/issues/comments/219214462","html_url":"https://github.com/i3/i3lock/issues/46#issuecomment-219214462","issue_url":"https://api.github.com/repos/i3/i3lock/issues/46","id":219214462,"user":{"login":"sandsmark","id":25765,"avatar_url":"https://avatars.githubusercontent.com/u/25765?v=3","gravatar_id":"","url":"https://api.github.com/users/sandsmark","html_url":"https://github.com/sandsmark","followers_url":"https://api.github.com/users/sandsmark/followers","following_url":"https://api.github.com/users/sandsmark/following{/other_user}","gists_url":"https://api.github.com/users/sandsmark/gists{/gist_id}","starred_url":"https://api.github.com/users/sandsmark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sandsmark/subscriptions","organizations_url":"https://api.github.com/users/sandsmark/orgs","repos_url":"https://api.github.com/users/sandsmark/repos","events_url":"https://api.github.com/users/sandsmark/events{/privacy}","received_events_url":"https://api.github.com/users/sandsmark/received_events","type":"User","site_admin":false},"created_at":"2016-05-14T11:06:44Z","updated_at":"2016-05-14T11:06:44Z","body":"tcatm, did you verify that it was the same thread/pid?\r\n\r\nI also experience this from time to time, but I haven't found any way to consistently reproduce it, which is to be expected if it is memory clobbering I guess. I think I'll try to reduce this to a smaller test case that can be run quickly in a loop."}}