Re: [fluid-dev] FluidSynth 1.1.x affected by a glib-2.22 bug

[Pedro Lopez-Cabanillas]

On Saturday, July 10, 2010, David Henningsson wrote:
> 2010-07-10 09:52, Pedro Lopez-Cabanillas skrev:
> > Hi,
> >
> > Since FS > 1.0.9, when changed to glib/gthread, FS users can suffer from
> > bugs on those libraries, like this one:
> >
> > https://bugzilla.gnome.org/show_bug.cgi?id=599079
> > https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/453898
> >
> >
> > $ chrt -f 50 fluidsynth -l -a alsa
> > FluidSynth version 1.1.1
> > Copyright (C) 2000-2009 Peter Hanappe and others.
> > Distributed under the LGPL license.
> > SoundFont(R) is a registered trademark of E-mu Systems, Inc.
> >
> >
> > GThread-ERROR **: file gthread-posix.c: line 348
> > (g_thread_create_posix_impl): error 'Invalid argument' during
> > 'pthread_attr_setschedparam (&attr, &sched)' aborting...
> > Aborted
> >
> >
> > This bug may be triggered not only when starting a program with chrt, but
> > also happens when kmid tries to launch fluidsynth at startup.
>
> Interesting. Whether the glib bug is fixed or not, why does kmid try to
> launch FluidSynth with rt priority (when this should be set via the
> settings "audio.realtime-prio" and "midi.realtime-prio")? If I
> understand correctly, that's the only way the bug can occur.

KMid does not try to launch FS with rt priority. Obviously, there are some 
possible scenarios having the same effect regarding this bug. In this case, 
KMid sets realtime priority for some of their own threads. This policy is 
inherited by FluidSynth when it is executed from one of those threads, 
triggering the bug. 

The attached program is another very simplified example of the problem 
(requires Qt4).

Regards,
Pedro

glibfluid.cpp
Description: Text Data