For every request, we do a suggested filename calculation. This is showing up in profiles as a major part of WebURLLoaderImpl::Context::OnReceivedResponse.
csharrison@ prepared an initial patch to make it not generated for everything [1]. When looking at it, we realized that the only reason we need this is for drag and drop: when an image is dragged out of Chrome into the file manager, we use the suggestedFilename calculated in OnReceivedResponse().
This is really wasteful and it doesn't make any sense to do it here: we should be doing this work in the browser-side instead, especially since the browser-side already *also* calls GetSuggetedFilename in some paths [2].
[1] https://codereview.chromium.org/2398053003/
[2] https://cs.chromium.org/chromium/src/content/browser/web_contents/web_contents_view_aura.cc?rcl=0&l=153
Comment 1 by pwnall@chromium.org
, Oct 31 2016