One example this might be causing: http://crbug/690029

i dug a bit deeper: when calling the image-decoder, we do not provide a desired-size: https://cs.chromium.org/chromium/src/services/image_decoder/image_decoder_impl.cc?rcl=90d1657ffcf4eb720c60e572453477fad72377f9&l=70
For the ico fetching, this probably leads to loading the smallest size (which is too small to be shown on the NTP).

If we want to support multiple resolutions, we need a different way to decode the image (collecting all frames).

Why is loading the largest size the wrong hack for http://crbug/690029, now?