<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PulseAudio gets reliably killed upon a big number of client connections" href="https://bugs.freedesktop.org/show_bug.cgi?id=94629#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PulseAudio gets reliably killed upon a big number of client connections" href="https://bugs.freedesktop.org/show_bug.cgi?id=94629">bug 94629</a> from <a class="email" href="mailto:patrakov@gmail.com" title="Alexander E. Patrakov <patrakov@gmail.com>"> Alexander E. Patrakov</a> <pre>(In reply to Ahmed S. Darwish from <a href="show_bug.cgi?id=94629#c4">comment #4</a>) > 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 :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>