{"action":"created","issue":{"url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/41","repository_url":"https://api.github.com/repos/dpurgin/harbour-callrecorder","labels_url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/41/labels{/name}","comments_url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/41/comments","events_url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/41/events","html_url":"https://github.com/dpurgin/harbour-callrecorder/issues/41","id":115141381,"number":41,"title":"Sometimes harbour-callrecorderd starts to constantly use 100% of CPU","user":{"login":"Self-Perfection","id":3757038,"avatar_url":"https://avatars.githubusercontent.com/u/3757038?v=3","gravatar_id":"","url":"https://api.github.com/users/Self-Perfection","html_url":"https://github.com/Self-Perfection","followers_url":"https://api.github.com/users/Self-Perfection/followers","following_url":"https://api.github.com/users/Self-Perfection/following{/other_user}","gists_url":"https://api.github.com/users/Self-Perfection/gists{/gist_id}","starred_url":"https://api.github.com/users/Self-Perfection/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Self-Perfection/subscriptions","organizations_url":"https://api.github.com/users/Self-Perfection/orgs","repos_url":"https://api.github.com/users/Self-Perfection/repos","events_url":"https://api.github.com/users/Self-Perfection/events{/privacy}","received_events_url":"https://api.github.com/users/Self-Perfection/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2015-11-04T20:35:59Z","updated_at":"2016-10-06T11:06:25Z","closed_at":null,"body":"It seems that it somehow related to phone call events. Dunno whether it is caused by answering call, stopping call or maybe during call. A bit of diagnostis follows.\r\n\r\nHangs just one thread (see light weight process (thread) ID 4143):\r\n```\r\n$ ps -FLC harbour-callrecorderd\r\nUID        PID  PPID   LWP  C NLWP    SZ   RSS PSR STIME TTY          TIME CMD\r\nnemo      3989   863  3989  0    9 91611 12632   0 Nov02 ?        00:01:20 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4010  0    9 91611 12632   1 Nov02 ?        00:00:00 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4141  0    9 91611 12632   1 Nov02 ?        00:00:16 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4143  3    9 91611 12632   0 Nov02 ?        01:56:34 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4144  0    9 91611 12632   0 Nov02 ?        00:00:01 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4145  0    9 91611 12632   0 Nov02 ?        00:00:00 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4146  0    9 91611 12632   1 Nov02 ?        00:00:00 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4189  0    9 91611 12632   0 Nov02 ?        00:00:04 /usr/bin/harbour-callrecorderd\r\nnemo      3989   863  4259  0    9 91611 12632   0 Nov02 ?        00:00:00 /usr/bin/harbour-callrecorderd\r\n```\r\nIt seems hanged thread constantly tries to read something:\r\n```\r\n$ strace -tt -p 4143 |& head -10\r\nProcess 4143 attached\r\n23:26:04.652947 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.654900 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.655052 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.655236 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.655419 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.656334 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.656517 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.656670 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n23:26:04.656853 read(18, 0x4e4ffc58, 10) = -1 EAGAIN (Resource temporarily unavailable)\r\n```\r\nBut I don't have any idea what it tries to read:\r\n```\r\n$ ls -l /proc/4143/fd/18\r\nlr-x------ 1 nemo nemo 64 2015-11-04 23:00 /proc/4143/fd/18 -> pipe:[1770970]\r\n```\r\nSuch situation happened to me 2 or 3 times. Really annoying to find 2 hours after a call that your device is suddenly almost out of charge.\r\nP.S.: I'm still using 0.6.0 version, just learned there is newer release. But it does not look like 0.6.1 have related fixes."},"comment":{"url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/comments/251932200","html_url":"https://github.com/dpurgin/harbour-callrecorder/issues/41#issuecomment-251932200","issue_url":"https://api.github.com/repos/dpurgin/harbour-callrecorder/issues/41","id":251932200,"user":{"login":"dpurgin","id":8401313,"avatar_url":"https://avatars.githubusercontent.com/u/8401313?v=3","gravatar_id":"","url":"https://api.github.com/users/dpurgin","html_url":"https://github.com/dpurgin","followers_url":"https://api.github.com/users/dpurgin/followers","following_url":"https://api.github.com/users/dpurgin/following{/other_user}","gists_url":"https://api.github.com/users/dpurgin/gists{/gist_id}","starred_url":"https://api.github.com/users/dpurgin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dpurgin/subscriptions","organizations_url":"https://api.github.com/users/dpurgin/orgs","repos_url":"https://api.github.com/users/dpurgin/repos","events_url":"https://api.github.com/users/dpurgin/events{/privacy}","received_events_url":"https://api.github.com/users/dpurgin/received_events","type":"User","site_admin":false},"created_at":"2016-10-06T11:06:25Z","updated_at":"2016-10-06T11:06:25Z","body":"Thanks a lot for the log! It looks like the PulseAudio thread is somehow deadlocked after the call. I'll take a look at the code. "}}
{"actor":{"display_login":"dpurgin"}}