[ardour-dev] Locked Memory Limits

Reuben Martin reuben.m at gmail.com
Fri Jan 26 19:06:09 PST 2007

I was having a problem with Ardour crashing after adding 9 stereo
tracks. The problem turned out to be the limits on locked memory was
too low. I was off chasing red herrings because occasionally a window
would pop up saying I had reached the port limit for the jack daemon.
(which wasn't true) Perhaps there is a way to deal with this more
gracefully? i.e. not crash. If not, maybe at least there could be a
window pop up after starting ardour that gives a warning about locked
memory limits similar to the one given on the console. (I think people
generally ignore messages on the console that don't prevent a program
from starting)

After raising the locked memory limit the crash problem was fixed.
However, running ardour2 under gdb would still crash for some reason.
Here's the back trace it produced for what it's worth:

(gdb) start
Breakpoint 1 at 0x85a0096: file gtk2_ardour/main.cc, line 364.
Starting program: /usr/lib/ardour2/ardour-2.0beta11.1
Failed to read a valid object file image from memory.
main (argc=1, argv=0xbfb08e34) at gtk2_ardour/main.cc:364
364             vector<Glib::ustring> null_file_list;
(gdb) bt full
#0  main (argc=1, argv=0xbfb08e34) at gtk2_ardour/main.cc:364
        engine = (class ARDOUR::AudioEngine *) 0x86c2f09
        null_file_list =
{<std::_Vector_base<Glib::ustring,std::allocator<Glib::ustring> >> = {
    _M_impl = {<std::allocator<Glib::ustring>> =
{<__gnu_cxx::new_allocator<Glib::ustring>> = {<No data fields>}, <No
data fields>}, _M_start = 0x8350b67, _M_finish = 0xb7f6a6c8,
      _M_end_of_storage = 0x812bad6}}, <No data fields>}


More information about the Ardour-Dev mailing list