Ticket #68 (closed defect: invalid)

Opened 3 years ago

Last modified 2 years ago

Segfault when loading an ALSA sink with LADSPA plugins

Reported by: NeTo Owned by: lennart
Milestone: Component: module-alsa-*
Keywords: Cc: villapancho@…

Description

Pulseaudio segfaults at startup when trying to load an ALSA sink that uses one or more LADSPA plugins.

If a device like the following is added in /etc/asound.conf:

   pcm.ladspa {
       type ladspa
       slave.pcm "plughw:0,0";
       path "/usr/lib/ladspa";
       plugins [
           {
               label delay_5s
               input {
                   controls [ 0.8 0.3 ]
               }
           }
       ]
   }

   pcm.pladspa {
       type plug
       slave.pcm "ladspa";
   }

and loaded, for example, with the following in /etc/pulseaudio/default.pa:

load-module module-alsa-sink device=pladspa sink-name=pa_ladspa

Pulseaudio only outputs at startup:

Segmentation fault

Change History

Changed 3 years ago by ossman

Could you run that through gdb so that we can see where it crashes?

Changed 3 years ago by NeTo

This is the backtrace I get with gdb:

#0  0xb79a15cc in ladspa_descriptor ()
   from /usr/lib/ladspa/highpass_iir_1890.so
#1  0x00000003 in ?? ()
#2  0x00000004 in ?? ()
#3  0x00000003 in ?? ()
#4  0x00000002 in ?? ()
#5  0xb7d7083f in malloc () from /lib/tls/i686/cmov/libc.so.6
Previous frame inner to this frame (corrupt stack?)

As LADSPA plugin I used the Glame Highpass Analog Filter, from http://plugin.org.uk . The plugin works correctly when using the ALSA device directly (using aplay -D for example).

Changed 3 years ago by NeTo

  • cc villapancho@… added

Changed 3 years ago by lennart

  • status changed from new to assigned

This looks like a bug in the LADSPA module, not in PA.

Changed 3 years ago by lennart

could you please provide us with a longer backtrace (-v)? One with debug symbols enabled? Otherwise it might be difficult to help you with thus.

Changed 2 years ago by lennart

  • status changed from assigned to closed
  • resolution set to invalid

Closing this now because this seems to be a an issue in ALSA and we got no feedback in half a year.

Note: See TracTickets for help on using tickets.