We may be able to get a memory pressure event from chrome that we can listen for and act accordingly to preserve memory resources.
For example, if the user has opened multiple DevTools screens, all of those screen controllers may be collecting data from the VM and slowly increasing the overall DevTools memory consumption. If we are nearing OOM, we should shut down resources we aren't using (like screen controllers from inactive screens).
We likely want to warn the user that we are running low on memory and that we are going to destroy some data on other screens, otherwise they might get frustrated that the timeline trace or the CPU profile they were just looking is now gone.
We may be able to get a memory pressure event from chrome that we can listen for and act accordingly to preserve memory resources.
For example, if the user has opened multiple DevTools screens, all of those screen controllers may be collecting data from the VM and slowly increasing the overall DevTools memory consumption. If we are nearing OOM, we should shut down resources we aren't using (like screen controllers from inactive screens).
We likely want to warn the user that we are running low on memory and that we are going to destroy some data on other screens, otherwise they might get frustrated that the timeline trace or the CPU profile they were just looking is now gone.