This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Creating many windows and tabs at startup locks up the browser for some seconds #14082
Labels
initiative/perf
perf
priority/P4
Minor loss of function. Workaround usually present.
release-notes/include
stale
After single-webview was implemented, starting up with multiple windows and many tabs no longer locks up the browser for multiple minutes. However, the experience is still not very smooth.
The windows, and all the tabs for those windows are created at the same time. This results in an extremely high number of state changes to be communicated from browser -> window, an extremely high number of actions to be dispatched in the browser and sent to the window to be dispatched, and a high number of frame changes which are sent from the window back to the browser (and then sent to the window again upon state diff as the frames are added to the app state too).
This results in a lockup for a few seconds whereby, whilst some events get through, the browser and the windows all spend most of their time diffing and patching state changes, and processing individual actions for each tab.
Some ways to get around this:
tab-inserted-at
?)Description
Steps to Reproduce
Most obvious, but happens with any number of tabs really:
Actual result:
Tabs take many seconds to show up in windows, window rendering is thrashy, window titles in app's window menu changes
Expected result:
Windows open, shortly and smoothly followed by a full set of tabs.
Reproduces how often:
100%
Brave Version
about:brave info:
0.22.703
Reproducible on current live release:
It's even worse on current release due to also rendering for and attaching a webview to each tab in each window.
The text was updated successfully, but these errors were encountered: