title: Does window.location.reload(true) affect javascript objects held in Internet explorer memory
body: <p>I am working on a memory leak issue in the Internet explorer. This is a single paged application that is displayed on a large screen and refreshed every thirty minutes using javascript <code>window.location.reload();</code>. After every refresh the memory size keeps on increasing. I suspect cross page leak in the application.
  More about it here.</p>
  
  <p><a href="https://github.com/webcomponents/webcomponentsjs/issues/541" rel="nofollow noreferrer">https://github.com/webcomponents/webcomponentsjs/issues/541</a>
  <a href="https://msdn.microsoft.com/en-us/library/bb250448(v=vs.85).aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/bb250448(v=vs.85).aspx</a> 
  <a href="https://stackoverflow.com/questions/2990484/javascript-memory-leak-on-page-refresh-remedy">Javascript memory leak on page refresh; remedy?</a></p>
  
  <p>But what I noticed was when I changed the code to <code>window.location.reload(true);</code> i.e hard refresh memory usage is normal and there is no memory leak.</p>
  
  <p>Now my question is when I am using <code>window.location.reload()</code> is it that other than using the cached javascript, Internet explorer also keeps the leaked javascript objects from the previous page in the Internet explorer memory while when  I am using <code>window.location.reload(true)</code> it not only gets fresh copies of the javascript files but clears any leaked objects held in the Internet explorer memory from the previous page. In short does hard refresh of a page affect the leaked objects held in Internet explorer memory related to that page.</p>