> Why is it not feasible to store and later rebuild the page DOM and view state? It is. It's called swap. They should just throttle the JS down to zero, and th

> Why is it not feasible to store and later rebuild the page DOM and view state? It is. It's called swap. They should just throttle the JS down to zero, and then let the OS deal with the memory. Each tab is a separate process. What they need is the opposite of mlock, a way to tell the OS to pretty please swap out this process's memory because it is unlikely to be used in the foreseeable future.