You are probably looking for a change made after 522407 (known good), but no later than 522408 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/8448affe3471114a8be3a25198083c6f8ab3f103..eee88582b5300e34aa2ea56bc5da17457e67aa00

Suspecting: https://chromium.googlesource.com/chromium/src/+/eee88582b5300e34aa2ea56bc5da17457e67aa00

@mstensho: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
                      

I'll be able to take a look sooner if you provide a simplified HTML test case. I don't build full Chrome that often.

I can't get browsing history to show up when attempting to remove a person. Any other way to reproduce?

If not, please provide a reduced HTML test case.

Marking this as P2, since it's not a high-traffic surface or flow.

With no means of reproducing this, I can't do anything.

With response to comment #3:
Above issue is still reproducible on latest canary version 66.0.3346.0 (Official Build). Please refer below mentioned steps 

Precondition: Create a fresh user and do not login into browser.
Steps:
1.Launch chrome and navigate to chrome://settings/ > Import bookmarks and settings
2.Select a browser which has browsing history for e.g Firefox or IE, click on import button.
3.Click on avatar icon > Manage people, click on 'remove this person' from iron icon such that list of details appear, observe lats digit of browsing history.

Note: Browsing history range should be more then or 100 (i.e 3 digit)

Please refer attached screencast for the same

Thank you!

Please find attached long history.html file and video for reference 

Deleted: Long history.html.html 113 KB

Long history.html.html 113 KB View Download

Deleted: Actual_html.mov 7.1 MB

	Actual_html.mov 7.1 MB View Download

Reassigning to mstensho@ and friendly ping: is this actionable now? Thanks!

Thanks! I can reproduce this.

The suspected CL in #c1 is the one.

Further reductions should be possible, such as removing word-wrap:break-word. Although that is what causes the wrapping in the Chrome UI, the root cause seems to be that preferred min/max widths aren't recalculated when table cells change their contents.

Deleted: tc.html 506 bytes

tc.html 506 bytes View Download

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6b335696ddcf6980440759a57400c34db42a1a05

commit 6b335696ddcf6980440759a57400c34db42a1a05
Author: Morten Stenshorne <mstensho@chromium.org>
Date: Tue Apr 10 10:47:54 2018

Make sure table flex/grid items recalculate min/max widths.

We used to rely on this taking place lazily via
MinPreferredLogicalWidth(), but that method won't necessarily be called
if the table is a flex/grid item.

Bug:  810327 
Change-Id: Ic817bd109544d4b9e961552d0a3a38f127e6e548
Reviewed-on: https://chromium-review.googlesource.com/1000781
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549479}
[add] https://crrev.com/6b335696ddcf6980440759a57400c34db42a1a05/third_party/WebKit/LayoutTests/external/wpt/css/css-flexbox/table-as-item-change-cell.html
[modify] https://crrev.com/6b335696ddcf6980440759a57400c34db42a1a05/third_party/blink/renderer/core/layout/layout_table.cc

 Issue 845445  has been merged into this issue.

Issue 841197 has been merged into this issue.