Sometimes harbour-callrecorderd starts to constantly use 100% of CPU about harbour-callrecorder HOT 6 CLOSED

I have not noticed this issue since I had reported it. I suppose it was fixed by callrecorder or OS update. Let's consider it as resolved.

from harbour-callrecorder.

I observe exactly the same hang right now

$ rpm -q harbour-callrecorder
harbour-callrecorder-0.7.0-1.armv7hl
$ ps -FLC harbour-callrecorder
UID        PID  PPID   LWP  C NLWP    SZ   RSS PSR STIME TTY          TIME CMD
nemo     21514   861 21514  0    3 82032  7232   0 01:42 ?        00:00:29 /usr/bin/harbour-callrecorderd
nemo     21514   861 21527  0    3 82032  7232   0 01:42 ?        00:00:04 /usr/bin/harbour-callrecorderd
nemo     21514   861 21531 17    3 82032  7232   1 01:42 ?        02:59:45 /usr/bin/harbour-callrecorderd

from harbour-callrecorder.

That's odd. Are there any visible symptoms? Can you please upload the log from /home/nemo/.local/share/kz.dpurgin/harbour-callrecorder/log.txt or send it to me per email? It contains non-masked phone numbers though, so it might be privacy-sensitive.

from harbour-callrecorder.

I've sent you an e-mail with log fragment with events around the time of hanging. At 18:38 I got incoming call. When I reached my phone I noticed that it was hot. Luckily it was attached to PC for hours thus it was not discharged.

The call at 18:48 was recorded without sound of remote side (I hear only my voice and surrounding noise in the recording).

Consumed CPU time by daemon process suggests, that something went wrong at the time of previous call and harbour-callrecorderd was "hanging" since that moment.

Offtopic: while I was composing this reply I received my brand new Jolla C. Happy me. Probably OS call recording function would be enough for me and I won't use harbour-callrecorder on new device.

from harbour-callrecorder.

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.

from harbour-callrecorder.

I don't recall noticing this issue for past year. Let's consider it resolved again.

from harbour-callrecorder.