<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>How recent of a gcc does Manjaro use? It seems this may be either
sandy bridge CPU peculiarity (there was another one pertaining to
locking and unlocking where double unlock on a pthread caused
crash on sandy bridge but no other cpus) where it may be more
sensitive to things programmers should not be doing in the first
place, or this may stem from the increased sensitivity in the new
gcc.</p>
<p>At any rate, after studying the code, it seems that a struct
settings is instantiated (containing all the default init settings
for the synth), passed along to instantiate the synth but then
also immediately afterwards it is freed even though the synth
instantiates multiple threads and it may be that the data is freed
before the other potential thread that may be in charge of
actually instantiating the synth may be done reading data within
it (I haven't had a chance to study the code enough to fully
understand how the threading is done within the libfluidsynth
itself). At any rate, I changed the fluid~ code now where settings
is a private member of the class and is freed only once the actual
entire synth is freed, which should hopefully also solve the
problem of the memory leak.</p>
<p>Best,</p>
<p>Ico<br>
</p>
<br>
<div class="moz-cite-prefix">On 5/23/2016 7:39 AM, Albert Graef
wrote:<br>
</div>
<blockquote
cite="mid:CA+rUic2sxED4Su4Ypdr6kVFdbMf2fpNt-XG2-8sFDxTeOXQZrQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi Ico,<br>
<br>
I just tested it on Manjaro (Arch) 64 bit, using various
different soundfonts and fluidsynth 1.1.6 and it works without
a hitch for me. Maybe a broken libfluidsynth on Ubuntu?<br>
<br>
</div>
<div>Albert<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, May 23, 2016 at 12:31 AM, Ivica
Bukvic <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">All,
<div><br>
</div>
<div>It appears since sometime earlier this year (possibly
with upgrade to Ubuntu 15.10 and newer), fluid~ external
crashes as soon as you enable dac~. It worked perfectly
fine before. The backtrace is fairly cryptic suggesting
something is wrong with the libfluidsynth. Yet, other
apps that use it work just fine (e.g. Qsynth). To make
matters more complicated, fluid~ uses flext library,
although other externals work fine with the current
version of flext.</div>
<div><br>
</div>
<div>Below is the gdb backtrace:</div>
<div><br>
</div>
<div>
<div>#0 0x0000000000000000 in ?? ()</div>
<div>#1 0x00007fffdab6e691 in fluid_hashtable_lookup ()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#2 0x00007fffdab6f51e in ?? ()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#3 0x00007fffdab71448 in fluid_settings_getint ()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#4 0x00007fffdab6a026 in fluid_LADSPA_run ()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#5 0x00007fffdab7d3b7 in fluid_rvoice_mixer_render
()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#6 0x00007fffdab8399d in fluid_synth_write_float
()</div>
<div> from
/usr/lib/x86_64-linux-gnu/libfluidsynth.so.1</div>
<div>#7 0x00007fffdae28908 in fluid::m_signal(int,
float* const*, float* const*) ()</div>
<div> from
/usr/lib/pd-l2ork/extra/flext/fluid~.pd_linux</div>
<div>#8 0x00007fffdae29fcb in
flext_dsp_multi::dspmeth(long*) ()</div>
<div> from
/usr/lib/pd-l2ork/extra/flext/fluid~.pd_linux</div>
<div>#9 0x00000000004b3bc5 in dsp_tick () at
d_ugen.c:336</div>
<div>#10 0x00000000004a3093 in sched_tick () at
m_sched.c:385</div>
<div>#11 0x00000000004a34be in m_pollingscheduler () at
m_sched.c:485</div>
<div>#12 m_mainloop () at m_sched.c:563</div>
</div>
<div><br>
</div>
<div>Is this a know issue? It wasn't a problem until I
upgraded to 15.10 (from 14.04) and it seems 16.04
(64bit) is also problematic. Has anyone had any luck
recently with the fluid~ external?</div>
</div>
<br>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a><br>
<a moz-do-not-send="true"
href="http://disis.music.vt.edu/listinfo/l2ork-dev"
rel="noreferrer" target="_blank">http://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature">
<div dir="ltr">Dr. Albert Gr"af<br>
Computer Music Research Group, JGU Mainz, Germany<br>
Email: <a moz-do-not-send="true"
href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a><br>
WWW: <a moz-do-not-send="true"
href="https://plus.google.com/+AlbertGraef"
target="_blank">https://plus.google.com/+AlbertGraef</a></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
L2Ork-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class="moz-txt-link-freetext" href="http://disis.music.vt.edu/listinfo/l2ork-dev">http://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
</blockquote>
<br>
</body>
</html>