There currently is a hardcoded limit of two live tabs. When opening a third tab, the webview for the least recently consulted tab is destroyed to free up memory. This limit could probably be made a configurable setting, and ideally we shouldn’t have to do that at all, but we’re currently hitting an issue where the system’s out-of-memory handler tends to select the process for the current tab when killing processes to release memory, having the undesirable effect that the current tab goes blank. There needs to be a way for oxide to instruct the system about which renderer process to kill first.
There currently is a hardcoded limit of two live tabs. When opening a third tab, the webview for the least recently consulted tab is destroyed to free up memory. This limit could probably be made a configurable setting, and ideally we shouldn’t have to do that at all, but we’re currently hitting an issue where the system’s out-of-memory handler tends to select the process for the current tab when killing processes to release memory, having the undesirable effect that the current tab goes blank. There needs to be a way for oxide to instruct the system about which renderer process to kill first.