divide large text runs into smaller runs to avoid chrome hangs
Categories
(Core :: Layout: Text and Fonts, defect, P3)
Tracking
()
People
(Reporter: jtd, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
Comment 1•11 years ago
|
||
Reporter | ||
Comment 3•11 years ago
|
||
Updated•11 years ago
|
Comment 5•9 years ago
|
||
Comment 7•3 years ago
|
||
Hi John,
Sorry for the old poke, I'm aware that this is an old report, but I'd like to close it if the issue no longer occurs.
Have you by any chance seen this issue on the latest Firefox versions?
Thank you!
Comment 8•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:jfkthame, since the bug has high severity and recent activity, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 9•2 years ago
|
||
I think we should close this as incomplete at this point. The specific log files referenced here and in bug 1228469, for example, are long gone, so direct comparisons to current behavior are difficult.
It's definitely still true that loading a huge log file can have noticeable delays; e.g. https://share.firefox.dev/3MoAQGD is a profile of loading https://firefoxci.taskcluster-artifacts.net/EOpL-WzTRC2Duw9EZJ2vqQ/0/public/logs/live_backing.log in Nightly on macOS, and shows a 5.5-second reflow. However, e10s means that this doesn't hang the entire browser UI (just the tab).
If we want to look into this further I think it would be best to open a new bug with suitable test files (as attachments, so they don't go away!) and profiles etc.
Description
•