Carriage return perf #6304
Fixes #4202, for real this time. Boy, it's kind of tricky to debug something for which the test case locks up the browser. The problem was essentially a bad cached value. We were overwriting carriage returns and backspaces correctly, but then not updating the cached value of the overwritten output stream. This meant that we were doing the same work, over, and over, and over, in a quadratically growing fashion.
The real fix for this is a one-liner in b899ab0 . The rest of this PR is just some cleanup.
Restructuring of private functionality.
None, except that the browser won't lock up when using progress bars.
The text was updated successfully, but these errors were encountered:
characters so we don't have to remove them over and over again.