I keep getting a memory error on my newer, faster laptop, yet everything works fine on my old, slow desktop


I’ve been using Ardour most of the year to mix with on my old P4 with not even a whole GB of RAM running Ubuntu 8.04. Sometimes the user malfunctions greatly, but generally it runs fine.

I recently got a HP/Compaq 65106, Core 2, just over 2 GB of RAM and a 1TB portable hard drive so I can work with a little portability. I’m running the 64 bit version of Ubuntu 9.04, and I can barely load all of my tracks before I get the polite message that my computer dosen’t have enough memory. I’m also having a hard time running Blender.

This is odd as I can run these programs very well on a computer that has exponentially less capacity than the system that says I don’t have enough memory.

Is anyone else having this problem?

Thanks in advance.

What do you get when you hit “free” in terminal?

Also make sure that /etc/security/limits.conf has “@audio - memlock unlimited” (or somewhere near 2gb).

Below are the results of my two searches, I didn’t see an @audio in the /ect/security/… Can I write it in, or does that reflect that there’s something else I need to download/install?


snowmiser@snowmiser-laptop:~$ sudo free

         total       used       free     shared    buffers     cached

Mem: 2026456 786092 1240364 0 18356 340696
-/+ buffers/cache: 427040 1599416
Swap: 3871624 0 3871624



#Each line describes a limit for a user in the form:


# can be:

- an user name

- a group name, with @group syntax

- the wildcard *, for default entry

- the wildcard %, can be also used with %group syntax,

for maxlogin limit

- NOTE: group and wildcard limits are not applied to root.

To apply a limit to the root user, must be

the literal username root.

# can have the two values:

- “soft” for enforcing the soft limits

- “hard” for enforcing hard limits

# can be one of the following:

- core - limits the core file size (KB)

- data - max data size (KB)

- fsize - maximum filesize (KB)

- memlock - max locked-in-memory address space (KB)

- nofile - max number of open files

- rss - max resident set size (KB)

- stack - max stack size (KB)

- cpu - max CPU time (MIN)

- nproc - max number of processes

- as - address space limit (KB)

- maxlogins - max number of logins for this user

- maxsyslogins - max number of logins on the system

- priority - the priority to run user process with

- locks - max number of file locks the user can hold

- sigpending - max number of pending signals

- msgqueue - max memory used by POSIX message queues (bytes)

- nice - max nice priority allowed to raise to values: [-20, 19]

- rtprio - max realtime priority

- chroot - change root to directory (Debian-specific)


#* soft core 0
#root hard core 100000
#* hard rss 10000
#@student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
#ftp hard nproc 0
#ftp - chroot /ftp
#@student - maxlogins 4

End of file

Hi, it seems your memory is recognised ok, unlike in my laptop where dust sometimes makes odd tricks.

Try adding these lines to /etc/security/limits.conf (e.g. just before “# End of file”)

@audio - rtprio 99
@audio - memlock unlimited
@audio - nice -10

(If somebody has better ideas, please tell.)