[pulseaudio-tickets] [Bug 94629] PulseAudio gets reliably killed upon a big number of client connections

[bugzilla-daemon at freedesktop.org]

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

--- Comment #5 from Alexander E. Patrakov <patrakov at gmail.com> ---
(In reply to Ahmed S. Darwish from comment #4)
> Sorry, my knowledge in this area is limited, but can we program
> PA to dynamically stop accepting more clients when it's close to
> approaching its realtime CPU limit?

No. The problem is not only with the number of clients. In steady state,
PulseAudio may well support, say, 45 clients. However, if a client triggers
rewinds often (either by changing its own volume frequently or by providing
non-zero as the last two parameters of pa_stream_write()), that's much more
work for PulseAudio. In other words, this is not only about not accepting new
clients, but about stopping processing on behalf of already-connected clients
that started behaving abusively.

I encourage you to try to write such abusive client, just to see whether you
can kill PulseAudio on your hardware using just two clients :)

-- 
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/20160320/2ad552d9/attachment.html>