VS 2015 MVC OutOfMemoryException
<p>Trying to debug an MVC5 web app - quite basic.  I've read articles and SO questions and answers and tried things until I'm blue in the face, and still can't figure out why I'm getting this error.</p>

<blockquote>
  <p>Exception of type 'System.OutOfMemoryException' was thrown.</p>
  
  <p>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. </p>
</blockquote>

<p>Environment:
- VS 2015
- Windows 10 Professional N
- IISExpress
- MVC5 Web Application</p>

<p>I used VS 2013 up until about two weeks ago, switched to 2015 after an upgrade to Windows 10.  I've never seen this until switching to 2015.  The project(s) are hardly large and memory consuming, the database probably has a dozen tables with two dozen rows in it, and it's not even this single project (this just happens to be my most active one at the moment).</p>

<p>I've done the following:</p>

<ul>
<li>Verified no spikes in machine resources when this occurs (CPU &lt; 10%, 14gb memory, pretty much flatlined at 6.7gb usage when trying start the debugging (same as normal when I'm not trying to start, no spikes at all))</li>
<li>Played with debug settings sufficient to ensure that IISExpress doesn't stay running in the background after I close the session/stop debugging.</li>
<li>Put IISExpress on the system try where I can manually stop application and close it</li>
<li>Verified that there's no hanging processes of iisexpress continuing to run3</li>
<li>Cleared out every temp folder and every other trick I've read about</li>
</ul>

<p>Yet, every three or four times I hit F5 to start debugging, I get this error.  Sometimes I can see IISExpress running, kill it and retry and it works fine.  Sometimes the only thing that works is restarting Visual Studio.</p>

<p>I go through runs where I have to restart VS every other time I want to debug the application.  This is insane, and I can't find the slightest trace of a cause.</p>

<p>I'm at my wits end, enough to the point where I'm thinking this has to be a bug with VS2015, possibly when running on Windows 10 Professional (N)?</p>

<p>Anyone?  Please?!?!  (can provide full stack trace if someone thinks it helpful)</p>