Caused by “Coverage counting path renderer”

Commit: ebce2b652a48bd3d3195dcf03379d723c8f47cd4 (Part of a Skia roll - actual CL was https://skia-review.googlesource.com/c/21541)

Link to size graph: https://chromeperf.appspot.com/report?sid=a097e74b1aa288511afb4cb616efe0f95ba4d347ad61d5e835072f23450938ba&num_points=10&rev=486970

Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase

The growth came entirely from native code.

It's not clear to me whether or not this increase was expected.
Please have a look and either:

Close as “Won't Fix” with a short justification, or
Land a revert / fix-up.
 

Caused by “Coverage counting path renderer”

Commit: ebce2b652a48bd3d3195dcf03379d723c8f47cd4 (Part of a Skia roll - actual CL was https://skia-review.googlesource.com/c/21541)

Link to size graph: https://chromeperf.appspot.com/report?sid=a097e74b1aa288511afb4cb616efe0f95ba4d347ad61d5e835072f23450938ba&num_points=10&rev=486970

Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase

The growth came entirely from native code.

It's not clear to me whether or not this increase was expected. Please have a look and either:

Close as “Won't Fix” with a short justification, or land a revert / fix-up.