+dnj

I believe logdog is going to solve this and it's close to being available everywhere. Dan, feel free to add more.

Kind of. The LogDog viewer still currently renders full logs, meaning it will likely hit the same problem. However, improvements to the viewer or other tooling that wants to use the API could certainly use the "Tail" API to build the log backwards. I have no specific plans to implement this right now, though.

Or maybe serve the file as pure text instead of html. It looks like the slowness comes from rendering the file as html (apparently a html with 40k+ <p> block is slow to render).

You can view any log as text by appending "/text" to the end of its URL.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

LogDog UI now has "tail", so I guess this fix fixed.

hinoka@ / dnj@ can you confirm?

it has the capability but it is not the default.  But there have been rendering fixes since last year.  Can the OP still find a stdio log that is difficult to render?