New issue
Advanced search Search tips

Issue 854164 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 852773
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Significant performance regression when printing multi-page table with dotted border

Reported by qu...@swydo.com, Jun 19 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3451.0 Safari/537.36

Steps to reproduce the problem:
1. Create a table with a <thead> containing many rows (the more the better).
2. Add <table> style "border-collapse: collapse;" and <tr> style "border-top: 1px solid #000".
3. Print the page, observe great performance.
4. Change <tr> style to "border-top: 1px dotted #000".
5. Print the page, observe performance is significantly worse.

To narrow down the issue further:
6. Add <thead> style "display: table-row-group;"
7. Print page, observe performance is similar to solid border.

What is the expected behavior?
Performance printing solid borders and dotted borders should be similar, even when table headers are repeating.

What went wrong?
There is a significant performance penalty when using dotted table row borders when table headers are repeated on multiple pages.

Did this work before? Yes 67.0.3396.87

Chrome version: 69.0.3451.0  Channel: dev
OS Version: OS X 10.13.3
Flash Version: 

We're also seeing this issue on Linux 68.0.3440.17.

In our testing with approx. 2000 rows the performance difference is very significant. The "solid border" and "no repeating headers" documents are printed in < 1s, while the "dotted border" document takes over ten seconds.
 
slow_print_dotted_border.html
58.3 KB View Download
slow_print_solid_border.html
58.4 KB View Download
slow_print_no_reapeat_header.html
58.4 KB View Download
Labels: Needs-Bisect Needs-Triage-M69
Cc: thestig@chromium.org pbomm...@chromium.org rbpotter@chromium.org
Components: Internals>Printing
Cc: phanindra.mandapaka@chromium.org
Labels: -Type-Bug -Pri-2 -Needs-Bisect hasbisect-per-revision Triaged-ET M-69 RegressedIn-69 ReleaseBlock-Beta Target-69 FoundIn-69 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on the reported chrome 69.0.3451.0,latest chrome 69.0.3466.0 using Mac OS 10.13.5,Windows10,Ubuntu17.10. Below is the bisect information for same.

Bisect Info:
================
Good build: 69.0.3446.0
Bad build: 69.0.3447.0

CHANGELOG URL:https://chromium.googlesource.com/chromium/src/+log/858211c2dfafafdee23d0d0ed8ac09f87ec0ce6d..4ed270af2dfc4dc15c8306978c6774031a0ad1db

Suspect: https://chromium.googlesource.com/chromium/src/+/4ed270af2dfc4dc15c8306978c6774031a0ad1db

Reviewed-on: https://chromium-review.googlesource.com/1079454

wangxianzhu:Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks!
Mergedinto: 852773
Status: Duplicate (was: Assigned)

Sign in to add a comment