#512: module-jack-sink segfault ----------------------------+----------------------------------------------- Reporter: matth45 | Owner: lennart Type: defect | Status: new Priority: high | Milestone: Component: module-jack-* | Severity: major Resolution: | Keywords: segfault jackd disconnect zombified ----------------------------+-----------------------------------------------
Comment(by matth45): I notice that if I start jackd with a larger period (eg. 4096) as: {{{ /usr/bin/jackd -v -R -p128 -dalsa -dhw:0 -r48000 -p4096 -n2 -P -S -o2 }}} I do not get disconnects. (I do get higher latency). I also get the following messages repeated as long as a client is connected to the pulseaudio daemon: {{{ D: memblock.c: Memory block too large for pool: 98304 > 65536 D: memblock.c: Memory block too large for pool: 98304 > 65536 D: memblock.c: Memory block too large for pool: 98304 > 65536 D: memblock.c: Memory block too large for pool: 98304 > 65536 }}} When I attempt to set shm-size-bytes in daemon.conf much larger that 1024*1024*64 pulseaudio fails to start with the message: {{{ E: shm.c: Assertion 'size <= ((pa_align(1024*1024*64)))' failed at pulsecore/shm.c:93, function pa_shm_create_rw(). Aborting. Aborted }}} A period of even 2048 still causes the frequent disconnects as seen above. -- Ticket URL: <http://pulseaudio.org/ticket/512#comment:2> PulseAudio <http://pulseaudio.org/> The PulseAudio Sound Server _______________________________________________ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets