title: Every other refresh causes "Aw, snap" error on Chrome, hard refresh doesn't
body: <p>We're developing a web app with Redux using react-redux. This web app deals with a substantial amount of data. Our tester noted that every other (normal) refresh causes an "Aw, snap" error in Chrome. Refreshing at that point will reload the page, but then refreshing again will cause the crash. Hard-refreshing (ctrl + f5), which bypasses the local cache, leads to a successful refresh every time. We do some things on window unload, including <code>navigator.sendBeacon</code>, but after commenting out those things the problem persists.</p>
  
  <p>Thinking that it may be an out of memory exception, I've tried memory profiling with Chrome devtools, but it disconnects when the "Aw, snap" error occurs. When the refresh is successful, I don't know how to look at the data.</p>
  
  <p>I've tried the Chrome logging detailed in this <a href="https://stackoverflow.com/questions/1728483/how-to-get-more-info-when-the-aw-snap-screen-shows-up-in-chrome">SO question</a> and this <a href="http://www.chromium.org/for-testers/enable-logging" rel="nofollow noreferrer">Chromium wiki</a> to no avail.</p>
  
  <p>What should I investigate next? What does it tell me that a hard refresh always works but a soft one fails every other time? Do I have local cache problems? Please comment if you have more questions about details with my setup.</p>