Well I understand but what I observe is that JACK has unpredictable amount of total clients which is an issue, regardless if it's closer to 10 than 1000.

- compilation flags, which by the way may cause jack to segfault if they are set too high

09.06.2016 1:39 PM "Paul Davis" <paul@linuxaudiosystems.com> napisał(a):

shared memory is not a very malleable resource. you can't just arbitrarily increase the size of it like you can with heap memory.

But running 250 JACK clients is not a viable workflow either. It doesn't scale in that way unless you're not interested in latency, in which case use PulseAudio.

On Thu, Jun 9, 2016 at 6:32 AM, marcin@saepia.net <marcin@saepia.net> wrote:
Hello,

I've found a piece of code that can be responsible for this:

#define MAX_SHM_ID 256

This is used to determine size of the registry.

What is rationale for hardcoding this like this?

m.

2016-06-09 12:02 GMT+02:00 marcin@saepia.net <marcin@saepia.net>:
Hello,

at some point I am getting the following errors from JACK

Jun 9 11:57:19 001-can1-plumber jackd[21110]: shm registry full
Jun 9 11:57:19 001-can1-plumber jackd[21110]: Cannot create shared memory segment of size = 422
Jun 9 11:57:19 001-can1-plumber jackd[21110]: JackShmMem::new bad alloc
Jun 9 11:57:19 001-can1-plumber jackd[21110]: Cannot open client
Jun 9 11:57:19 001-can1-plumber jackd[21110]: Cannot create new client

Max locked memory for this process is set to 134217728 while launching JACK via systemd.

It effectively causes JACK to hang.

I am using 1.9.10 (commit 1ed50c92) on ubuntu 16.04.

The configure flags are --clients=500 --ports-per-application=4 (I am not reaching 500 clients limit when that occurs, they are around 250).

JACK is started with dummy driver, and --port-max set to 2000.

What is the reason for hitting SHM limit? Can I overcome this in any way?

m.

_______________________________________________
Jack-Devel mailing list
Jack-Devel@lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org