Bug 538472 - AO: [pulse] Init failed: Too large
Summary: AO: [pulse] Init failed: Too large
Keywords:
Status: CLOSED DUPLICATE of bug 554568
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 11
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 16:40 UTC by Bill C. Riemers
Modified: 2018-04-11 18:05 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-23 02:35:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
requested information (64.06 KB, text/plain)
2009-12-02 16:43 UTC, Matěj Cepl
no flags Details

Description Bill C. Riemers 2009-11-18 16:40:57 UTC
Description of problem:

The following bug seems related to 488365 and it's duplicate.   Only those bugs are listed as "fixed" while this is a new issue.

When attempting to play a wave file with mplayer I am getting the following errors:

[pulse] working around probably broken pause functionality,
        see http://www.pulseaudio.org/ticket/440
AO: [pulse] Init failed: Too large
Failed to initialize audio driver 'pulse'

Version-Release number of selected component (if applicable):

pulseaudio-libs-glib2-0.9.15-17.fc11.x86_64
pulseaudio-0.9.15-17.fc11.x86_64
pulseaudio-esound-compat-0.9.15-17.fc11.x86_64
pulseaudio-libs-0.9.15-17.fc11.i586
pulseaudio-module-x11-0.9.15-17.fc11.x86_64
pulseaudio-libs-zeroconf-0.9.15-17.fc11.x86_64
pulseaudio-libs-0.9.15-17.fc11.x86_64
alsa-plugins-pulseaudio-1.0.21-2.fc11.x86_64
pulseaudio-module-gconf-0.9.15-17.fc11.x86_64
pulseaudio-utils-0.9.15-17.fc11.x86_64
mplayer-1.0-0.110.20090329svn.fc11.x86_64

How reproducible:

100% of the time today.  This also seems to effect applications like "konversation".   I have heard sound from konversation before under Fedora 11, so either this is a new issue, or it is transient.

Steps to Reproduce:
1. From a shell prompt run, "mplayer /usr/share/sounds/error.wav"
2.
3.
  
Actual results:

No sound heard.   The following was output to the console:

MPlayer 29092-4.4.1 (C) 2000-2009 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /usr/share/sounds/error.wav.
Audio only file format detected.
==========================================================================
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 1411.2 kbit/100.00% (ratio: 176400->176400)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[pulse] working around probably broken pause functionality,
        see http://www.pulseaudio.org/ticket/440
AO: [pulse] Init failed: Too large
Failed to initialize audio driver 'pulse'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video


Exiting... (End of file)

Expected results:

I expect to hear sound, or at least get a message that indicates what I need to fix in order to hear sound.

Additional info:

I also tried using alsa:

[docbill@hartnell ~]$ mplayer -ao alsa /usr/share/sounds/error.wav
MPlayer 29092-4.4.1 (C) 2000-2009 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /usr/share/sounds/error.wav.
Audio only file format detected.
==========================================================================
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 1411.2 kbit/100.00% (ratio: 176400->176400)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_pulse.c:724:(pulse_prepare) PulseAudio: Unable to create stream: Too large

[AO_ALSA] Unable to set hw-parameters: Input/output error
Failed to initialize audio driver 'alsa'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video


Exiting... (End of file)

Comment 1 Lennart Poettering 2009-11-19 23:55:16 UTC
Hmm "Too large" is actually a badly named error that indicates that there is some kind of limit on streams (or other kind of resources) reached.

Could you please provide the output of "pacmd ls" when this happens? This should give us a hint which application might have created so many streams that PA refuses to take another one.

Comment 2 Bill C. Riemers 2009-11-20 15:34:39 UTC
I haven't seen this problem again since rebooting my machine.  However, I will report this information next time this error occurs.

Bill

Comment 3 Matěj Cepl 2009-12-02 16:43:53 UTC
Created attachment 375485 [details]
requested information

(In reply to comment #1)
> Could you please provide the output of "pacmd ls" when this happens? This
> should give us a hint which application might have created so many streams that
> PA refuses to take another one.  

here we are

Comment 4 Matěj Cepl 2009-12-02 16:48:15 UTC
and yes:

bradford:~$ pgrep -f -l aplay
24574 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24577 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24580 aplay -q /usr/share/gajim/data/sounds/sent.wav
24584 aplay -q /usr/share/gajim/data/sounds/connected.wav
24598 aplay -q /usr/share/gajim/data/sounds/connected.wav
24604 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24629 aplay -q /usr/share/gajim/data/sounds/sent.wav
24639 aplay -q /usr/share/gajim/data/sounds/connected.wav
24642 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24656 aplay -q /usr/share/gajim/data/sounds/sent.wav
24670 aplay -q /usr/share/gajim/data/sounds/gc_message1.wav
24722 aplay -q /usr/share/gajim/data/sounds/sent.wav
24726 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24745 aplay -q /usr/share/gajim/data/sounds/gc_message1.wav
24750 aplay -q /usr/share/gajim/data/sounds/connected.wav
24777 aplay -q /usr/share/gajim/data/sounds/connected.wav
24813 aplay -q /usr/share/gajim/data/sounds/connected.wav
24816 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24819 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24833 aplay -q /usr/share/gajim/data/sounds/sent.wav
24838 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24859 aplay -q /usr/share/gajim/data/sounds/connected.wav
24865 aplay -q /usr/share/gajim/data/sounds/connected.wav
24885 aplay -q /usr/share/gajim/data/sounds/connected.wav
24889 aplay -q /usr/share/gajim/data/sounds/sent.wav
24893 aplay -q /usr/share/gajim/data/sounds/sent.wav
24902 aplay -q /usr/share/gajim/data/sounds/disconnected.wav
24909 aplay -q /usr/share/gajim/data/sounds/sent.wav
24923 aplay -q /usr/share/gajim/data/sounds/sent.wav
24935 aplay -q /usr/share/gajim/data/sounds/sent.wav
24956 aplay -q /usr/share/gajim/data/sounds/sent.wav
24977 aplay -q /usr/share/gajim/data/sounds/sent.wav
bradford:~$

Comment 5 Matěj Cepl 2009-12-02 17:37:38 UTC
Hmm, I thought aplay does something wrong with pulseaudio, but paplay doesn't seem to work better:

bradford:~$ pgrep -f -l play
1880 /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1 --force-active-vt
29110 paplay /usr/share/gajim/data/sounds/disconnected.wav
29173 paplay /usr/share/gajim/data/sounds/disconnected.wav
29175 paplay /usr/share/gajim/data/sounds/sent.wav
29188 paplay /usr/share/gajim/data/sounds/disconnected.wav
29190 paplay /usr/share/gajim/data/sounds/disconnected.wav
29197 paplay /usr/share/gajim/data/sounds/connected.wav
29210 paplay /usr/share/gajim/data/sounds/connected.wav
29230 paplay /usr/share/gajim/data/sounds/connected.wav
29232 paplay /usr/share/gajim/data/sounds/disconnected.wav
29235 paplay /usr/share/gajim/data/sounds/disconnected.wav
29239 paplay /usr/share/gajim/data/sounds/gc_message1.wav
29244 paplay /usr/share/gajim/data/sounds/connected.wav
29279 paplay /usr/share/gajim/data/sounds/sent.wav
29283 paplay /usr/share/gajim/data/sounds/disconnected.wav
29300 paplay /usr/share/gajim/data/sounds/sent.wav
29306 paplay /usr/share/gajim/data/sounds/disconnected.wav
29334 paplay /usr/share/gajim/data/sounds/connected.wav
29336 paplay /usr/share/gajim/data/sounds/connected.wav
29339 paplay /usr/share/gajim/data/sounds/disconnected.wav
29344 paplay /usr/share/gajim/data/sounds/gc_message1.wav
29347 paplay /usr/share/gajim/data/sounds/disconnected.wav
29358 paplay /usr/share/gajim/data/sounds/sent.wav
29474 paplay /usr/share/gajim/data/sounds/connected.wav
29487 paplay /usr/share/gajim/data/sounds/connected.wav
29490 paplay /usr/share/gajim/data/sounds/connected.wav
29492 paplay /usr/share/gajim/data/sounds/disconnected.wav
29504 paplay /usr/share/gajim/data/sounds/message2.wav
29583 paplay /usr/share/gajim/data/sounds/disconnected.wav
29597 paplay /usr/share/gajim/data/sounds/disconnected.wav
29601 paplay /usr/share/gajim/data/sounds/disconnected.wav
29613 paplay /usr/share/gajim/data/sounds/connected.wav
29709 paplay /usr/share/gajim/data/sounds/connected.wav
bradford:~$

Comment 6 Matěj Cepl 2009-12-02 17:39:21 UTC
Hmm, and this time even

pkill -f paplay

didn't help. I had to do pulseaudio --kill ; pulseaudio -D again

Using
bradford:~$ rpm -qa \*pulse\*
pulseaudio-libs-zeroconf-0.9.21-1.fc12.x86_64
alsa-plugins-pulseaudio-1.0.21-2.fc12.i686
pulseaudio-utils-0.9.21-1.fc12.x86_64
pulseaudio-module-zeroconf-0.9.21-1.fc12.x86_64
alsa-plugins-pulseaudio-1.0.21-2.fc12.x86_64
pulseaudio-gdm-hooks-0.9.21-1.fc12.x86_64
pulseaudio-module-bluetooth-0.9.21-1.fc12.x86_64
pulseaudio-module-gconf-0.9.21-1.fc12.x86_64
pulseaudio-0.9.21-1.fc12.x86_64
pulseaudio-libs-0.9.21-1.fc12.i686
pulseaudio-libs-0.9.21-1.fc12.x86_64
pulseaudio-debuginfo-0.9.19-1.fc12.x86_64
pulseaudio-module-x11-0.9.21-1.fc12.x86_64
pulseaudio-libs-glib2-0.9.21-1.fc12.x86_64
bradford:~$

Comment 7 Lennart Poettering 2010-02-23 02:35:53 UTC
Matej, I am not sure where the problem is? We enforce a limit on streams that may be mixed. If you start that many paplay/aplay then yes, you will reach that limited. 

But otherwise I think this is actually the same issue as bug 554568 which I now fixed.

*** This bug has been marked as a duplicate of bug 554568 ***

Comment 8 Matěj Cepl 2010-02-23 14:32:20 UTC
Yeah, and I am not using gajim currently, so I am not able to reproduce easily. 

Hmm, I thought I would try to run a testing script like

#!/bin/sh

COUNTER=1000

while [ $COUNTER -gt 0 ] ; do
    paplay ~/Hudba/Sound_Clip/Ubuntu-startup.wav
done


but apparently on my RHEL6 paplay is completely broken (doesn't play at all; both aplay, totem, rhythmbox play as charm).

Anyway, this bug could probably go to rest.


Note You need to log in before you can comment on or make changes to this bug.