Re: [fluid-dev] Fun dbus crash

2012-02-28 Thread Corbin Simpson
Huh. With that argument, about half the time, the test works (I hear delightful synthesized piano). I'm getting more fun errors, like: process 13344: arguments to dbus_pending_call_free_data_slot() were incorrect, assertion "*slot_p >= 0" failed in file dbus-pending-call.c line 748. This is normal

Re: [fluid-dev] Fun dbus crash

2012-02-28 Thread Pedro Lopez-Cabanillas
On Tuesday 28 February 2012, Corbin Simpson wrote: > In the meantime, is there an easy way to hack around this in settings, > or do I need to rebuild FS without dbus support? Try with the environment variable MALLOC_CHECK_ set to 0 or 1. But this error message probably means a bug in either dbus,

[fluid-dev] Fun dbus crash

2012-02-28 Thread Corbin Simpson
Hey all, I know I've been super-silent on the FS front, but I got the bug in me today, so I revived my Python FS bindings. While hacking, I discovered this delightful crash: $ python test.py fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. *** glibc detected *** p