Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As discussed in the exchange of comments to the question: </p> <blockquote> <p>Strange thing is that I'm using 64bit MSBuild on 64bit Win7 laptop with 4GB of physical and "unlimited" virtual RAM. MSBuild process is using about 1GB of RAM (1,5GB peak). – Ludwo 4 hours ago</p> </blockquote> <blockquote> <p>I'm using 32bit MSBuild on a 32-bit WinXP desktop with 2GB of physical and similarly unlimited virtual RAM. The weird thing is that the crash occurs when physical RAM is completely used up. It's like I've got zero virtual memory! – Kevin Vermeer 3 hours ago </p> </blockquote> <blockquote> <p>Yes, it seems like MSBuild is not using virtual memory :) – Ludwo 2 hours ago</p> </blockquote> <p>It did seem like MSbuild wasn't using virtual memory. I did some tests (starting a bunch of programs) and it seemed like <em>nothing</em> was using virtual memory. I did some searches which lead me to check</p> <pre><code>Control Panel -&gt; System -&gt; Advanced -&gt; Performance -&gt; Advanced -&gt; Virtual Memory </code></pre> <p>and found that there exists a setting which limited my virtual memory size system-wide. I had imagined that virtual memory to be effectively infinite, or, more precisely, 4 GB for each process on 32-bit XP. I wasn't approaching this limit. However, my virtual memory space was limited to...0MB. Not cool, whoever or whatever did that.</p> <p>I changed this to allocate a minimum of 1024 MB and a maximum of 4096 MB of virtual memory. I added the "Virtual size" column in <a href="http://technet.microsoft.com/en-us/sysinternals/bb896653" rel="nofollow">Process Explorer</a>, which, together with the "System Commit" graph, demonstrates that I now use more memory than the amount available in the physical RAM sticks.</p> <p>This fixed my problems. Unfortunately, my system grinds to a near-halt whenever it tries to page any memory, but that's better than a crash. I did re-enable parallel builds; it parallelizes and uses lots of CPU while I have RAM left (which is true for most of the files) and dips to 1% of CPU usage when I have no more RAM. When those files are done, speed is restored.</p>
    singulars
    1. This table or related slice is empty.
    1. POerror MSB4166: Child node exited prematurely. Shutting down
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKevin Vermeer
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMy VM is enabled and system managed
      singulars
      1. PO
      1. USLudwo
    2. CO@Ludwo - That's a good thing, and there are certainly many possible causes for this sort of error, but have you tried setting it manually?
      singulars
      1. PO
      1. USKevin Vermeer
    3. COIt is not VM settings issue. I have 800MB of free memory. Now I will check if is it caused by 32bit extensions or not...
      singulars
      1. PO
      1. USLudwo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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