FluidSynth segfault when playing MIDI files

[derselbst]

Reported by Irányossy Knoblauch Artúr on the mailing list:
http://lists.gnu.org/archive/html/fluid-dev/2009-05/msg00024.html

Confirmed crash.

Traceback:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff20ec950 (LWP 2789)]
fluid_dsp_float_interpolate_4th_order (voice=0x60d620) at fluid_dsp_float.c:288
288 short int *dsp_data = voice->sample->data;

(gdb) backtrace

#0 fluid_dsp_float_interpolate_4th_order (voice=0x60d620)

at fluid_dsp_float.c:288

#1 0x00007ffff7d84f3d in fluid_voice_write (voice=0x60d620,

dsp_left_buf=0x70a660, dsp_right_buf=0x70a770, dsp_reverb_buf=0x70a8c0,
dsp_chorus_buf=0x70aae0) at fluid_voice.c:602

#2 0x00007ffff7d7e5b8 in fluid_synth_one_block (synth=0x608c30,

do_not_mix_fx_to_out=0) at fluid_synth.c:1963

#3 0x00007ffff7d7ea7e in fluid_synth_write_float (synth=0x608c30, len=128,

Reported by: elementgreen

Original Ticket: fluidsynth/tickets/43

[derselbst]

Original comment author: diwic

I'm currently completing a patch for this bug, by using the sequencer as a thread-safe buffer between the midi and audio thread, to avoid concurrency problems. I've been running the suggested test case for half an hour now and it has not crashed yet, so I'm optimistic.

Original comment by: elementgreen

[derselbst]

• status changed from new to closed
• resolution set to fixed

Original comment by: elementgreen