Thanks for filing!  Ken, can you help triage this to find an owner?

I should add that this only happens on high DPI.

Friendly ping.  Do we have a lead on how to fix, or anyone who may be able to help?

Ken/Fady: Can you also clarify whether there's a functional problem due to this bug, or if it's mainly a performance issue?

Feel free to re-add Component if the more specific is helpful later.

Fady: To clarify, does this mean that the main frame is scrolling, and the OOPIF is getting continuous resize messages because of rounding changes in the frame rect size in the parent's layout?

Do you know how this doesn't happen for local frames?

+fsamuel@

GPU triage: ping, what is the next step here?

Ohh I actually think I fixed this one a while ago.

https://chromium-review.googlesource.com/c/chromium/src/+/891663

The physical backing size is now a function of the "local frame size". The frame rect is no longer used. I'm marking this as FIXED. Yaay!

[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.

Is there any merge need to M66 or M65? Is yes, pls request a merge otherwise remove "Merge-TBD" label. Thank you.

I don't think there is anything further to do. The fix is on the 66 branch, and this isn't high enough priority to warrant a merge to 65.

Removing "Merge-TBD" label per comment #11. Thank you.