[pulseaudio-tickets] [Bug 96821] module-echo-cancel: aec_method='webrtc', pulseaudio gets killed with SIGKILL

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96821

--- Comment #4 from Antonio Ospite <ao2 at ao2.it> ---
(In reply to Arun Raghavan from comment #3)
> (In reply to Arun Raghavan from comment #1)
> [...]
> > What is CPU usage like in the working case? And can you see what it's like
> > before PA gets killed?

You are right, I didn't answer the question about CPU usage.

So, to recap, I am using the kernel from Debian, I am using pulseaudio 9.0 from
the Debian packages (but it's the same if I compile my own) like this: LANG=C
pulseaudio -v

LANg=C is needed here because of Bug #96819.

I load the echo-cancel module like this:

pactl load-module module-echo-cancel format=s16le rate=8000 channels=4
aec_method='webrtc' aec_args='"beamforming=1
mic_geometry=-0.03,0,0,-0.01,0,0,0.01,0,0,0.03,0,0"'

I start recording form the echo canceled source like this:
gst-launch-1.0 pulsesrc
device-name=alsa_input.usb-OmniVision_Technologies__Inc._USB_Camera-B4.04.27.1-01.multichannel-input.echo-cancel
! fakesink

and the pulseaudio CPU usage is between 6% and 7.3%

If I load the module with other values for the rate parameter, and do nothing
else pulseaudio gets killed after some seconds.

But I noticed that it stays alive if I start to record right after I loaded the
module, regardless of the format, I even tried with 48000. The CPU usage is
always in the range of 6-7.3% when recording.

What kind of logs should I send?
I will also try with the kinect  and see if I get the same behavior.

Thanks,
   Antonio

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20160728/940bff02/attachment.html>