Using the per-revision bisect providing the bisect results,
Good Build : 57.0.2928.0 (revision : 433845)
Bad Build : 57.0.2929.0 (revision : 434071)

You are probably looking for a change made after 433852 (known good), but no later than 433853 (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/c11607a50691c6da823467bb389d14f659433c77..79bd413143afe5ad68104a3c99b9c04f64fc25ac

From the CL above, assigning the issue to the concern owner 

@rego - 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.

Review-Url: https://codereview.chromium.org/2521953002

Note : As this is a recent regression , adding ReleaseBlock-Stable . Please feel free to edit/remove this.

Thanks!

I didn't investigate it deep enough, but the output is the very same if you have grid enabled on Firefox too.

The issue is that ".searchresultcontainer" is using "display: grid".
Changing it to "display: block" or "display: inline-grid" solves the issue.

I didn't investigate it further, not sure if it's worth or not.
But I'm not sure if they're using grid layout on purpose or not.
What should be the next steps?

BTW, a very similar issue appears if you use "display: flex" instead of "display: grid".

Can you minimize this test and figure out why it's different in Chrome vs Firefox?

Sorry--I misunderstood (missed the part about enabling grid in firefox). I guess this should be closed as wontfix. I'll try to contact Newegg about this as well.