Okay, here’s ANOTHER segmentation fault error. I finally got a decent amount of locked memory available for regular users, but now when I try to open an existing session I get the usual stuff, but then it crashes with:
I didn’t have access to my Ardour computer when I did the above post, but I’m at it now and here’s the complete startup output:
gene@lemon:~$ ardour2
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with ‘ulimit -l’, and it
is normally controlled by /etc/security/limits.conf
Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
loading default ui configuration file /usr/local/etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/gene/.ardour2/ardour2_ui.conf
Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
loading user configuration file /home/gene/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /home/gene/.ardour2/surfaces/:/usr/local/lib64/ardour2/surfaces/
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
ardour: [INFO]: Control protocol Tranzport not usable
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: “Mackie”
loading bindings from /usr/local/etc/ardour2/mnemonic-us.bindings
(ardour-2.8.11:2766): Gtk-WARNING **: EnableTranslation: missing action EnableTranslation
Session writable based on /home/gene/Ardour/Screaming at the Moon/
Segmentation fault (core dumped)
This is for a brand-new session; the only thing I did was create the session, close Ardour, and attempt to re-open it. I should have plenty of locked memory:
@2handband: 4096 is still ridiculously small! this is in kilobytes. Ardour needs many megabytes. Your system no doubt has many gigabytes. You should use something like ulimit -l unlimited or at least ulimit -l 1073741824 (the latter is 1GB). If you don’t use unlimited, at least use about 75% of your physical RAM.
You, sir, are the man. I’ve just done half a dozen session re-opens, all successful. Thanks! Hopefully all of my future questions will be in the how-to section…