[Ardour-Users] Ardour 3 - xruns and segfaults

Christian Weikusat christian at shamanbenefit.net
Wed Mar 27 11:40:34 PDT 2013

> my first suggestion would be to lower -n to 2 and increase -p to 1024. 
> this will provide you with the same latency you are currently working 
> with, but at much lower CPU overhead (fewer context switches).

Well, the latency is actually doubled (42.7 ms) but this seems to have solved the xrun problem!
Many thanks!!

On the downside:
I get even more segfaults (e.g. when saving projects, when quitting ardour3).

There is one project that reproducibly segfaults after ~2 seconds of playback, but it gives different errors on the terminal each time like


"(ardour-3.0:3579): glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: call to empty boost::function

Trace/Breakpoint ausgelöst"


"*** glibc detected *** /home/christian/pakete/audio/Ardour_64bit-3.0_14207/Ardour_x86_64-3.0_14207/bin/ardour-3.0: invalid fastbin entry (free): 0x00007f9466e9ebf0 ***

I try to attach the project to this email (it's 6.5 k).

Switching to just 1 processor it still segfaults.

Thanks for the answers!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rom.tar.xz
Type: application/octet-stream
Size: 6616 bytes
Desc: not available
URL: <http://lists.ardour.org/pipermail/ardour-users-ardour.org/attachments/20130327/f822a008/attachment-0002.obj>

More information about the Ardour-Users mailing list