Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Check with <code>file</code> and <code>ldd</code> that your executable is indeed 64 bits.</p> <p>Check also the resource limits. From inside the process, you could use <a href="http://linux.die.net/man/2/getrlimit" rel="nofollow">getrlimit</a> system call (and <code>setrlimit</code> to change them, when possible). From a <code>bash</code> shell, try <code>ulimit -a</code>. From a <code>zsh</code> shell try <code>limit</code>.</p> <p>Check also that your process indeed eats the memory you believe it does consume. If its pid is 1234 you could try <code>pmap 1234</code>. From inside the process you could read the <code>/proc/self/maps</code> or <code>/proc/1234/maps</code> (which you can read from a terminal). There is also the <code>/proc/self/smaps</code> or <code>/proc/1234/smaps</code> and <code>/proc/self/status</code> or <code>/proc/1234/status</code> and other files inside your <code>/proc/self/</code> ...</p> <p>Check with  <code>free</code> that you got the memory (and the swap space) you believe. You can add some temporary swap space with <code>swapon /tmp/someswapfile</code> (and use <code>mkswap</code> to initialize it).</p> <p>I was routinely able, a few months (and a couple of years) ago, to run a 7Gb process (a huge <code>cc1</code> compilation), under Gnu/Linux/Debian/Sid/AMD64, on a machine with 8Gb RAM.</p> <p>And you could try with a tiny test program, which e.g. allocates with <code>malloc</code> several memory chunks of e.g. 32Mb each. Don't forget to write some bytes inside (at least at each megabyte).</p> <p>standard C++ containers like <code>std::map</code> or <code>std::vector</code> are rumored to consume more memory than what we usually think.</p> <p>Buy more RAM if needed. It is quite cheap these days.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload