In current Firefox Nightly on my Lenovo ThinkPad, we spend about 5 seconds reflowing the page (during which time the tab is blank) and then we finish rendering and we're done. Profile: https://share.firefox.dev/3AtNLEr This doesn't seem particularly bad, particularly given that e10s will mean the frontend and most/all background tabs should remain responsive. Also, RE memory usage (which I imagine is why the original reporter's system came to a halt due to swapping): bz mentioned > 700MB RAM usage in comment 4 (possibly much more, he just killed the browser at that point), but my profile shows our content process peaking at about 250-260MB RAM. So we seem to have improved that metric here as well. So: I suspect we can consider this bug essentially fixed by a combination of e10s and various optimizations/improvements over the years.
Bug 367116 Comment 30 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In current Firefox Nightly on my Lenovo ThinkPad, we spend about 5 seconds reflowing the page (during which time the tab is blank) and then we finish rendering and we're done. Profile: https://share.firefox.dev/3ptF5aN This doesn't seem particularly bad, particularly given that e10s will mean the frontend and most/all background tabs should remain responsive. Also, RE memory usage (which I imagine is why the original reporter's system came to a halt due to swapping): bz mentioned > 700MB RAM usage in comment 4 (possibly much more, he just killed the browser at that point), but my profile shows our content process peaking at about 250-260MB RAM. So we seem to have improved that metric here as well. So: I suspect we can consider this bug essentially fixed by a combination of e10s and various optimizations/improvements over the years.