[pulseaudio-discuss] lots of [null-sink] memblock.c: Pool full

[wellington wallace]

Hi,

Today I noticed I have lots of these messages in Pulseaudio debug output:

jun 25 15:44:11 wwmm pulseaudio[1148]: D: [alsa-sink-ALC887-VD Analog]
ratelimit.c: 1685 events suppressed
jun 25 15:44:11 wwmm pulseaudio[1148]: D: [alsa-sink-ALC887-VD Analog]
memblock.c: Pool full
jun 25 15:44:11 wwmm pulseaudio[1148]: D: [null-sink] memblock.c: Pool full

They happen when I am using my application
https://github.com/wwmm/pulseeffects. In PulseEffects I load a null sink
and then launch a gstreamer pipeline where the pulsesrc plugin records from
the null sink monitor device. I wonder if I am doing something wrong. It
seems to me that these messages should not be there when everything is
alright. Is that so?

As someone new to the development of Pulseaudio applications I would also
like to ask what is the proper when to finish an application that is using
Pulseaudio. The documentation tells to disconnect from the context and I am
already doing that. Is there something else I should do when closing the
application? Like calling unref on context?

Best regards,

                     Wellington

-- 
Prof.° Wellington Wallace Miguel Melo

CEFET/RJ Uned Nova Iguaçu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20170625/ef7c4f61/attachment.html>