Time to save large file (Chromium issue)

imlitimlit

If I go to the fcc page to get all the am stations, it take a few minutes for the page to run.
It is about 9mb of data. Not a problem
Page:
https://transition.fcc.gov/fcc-bin/amq?call=&arn=&state=&city=&freq=530&fre2=1700&type=0&facid=&class=&list=4&ThisTab=Results+to+This+Page%2FTab&dist=&dlat2=&mlat2=&slat2=&NS=N&dlon2=&mlon2=&slon2=&EW=W&size=9

Once the page is fully loaded it takes about 3 minutes to save to disk. Why so long? Firefox takes a few seconds.

Pesala

@imlitimlit For me, using the latest Snapshot, the page is not saved at all. Trying to save it again does not throw up an overwrite message as one might expect.

As you say, Firefox saves it instantly (presumably from cache).

Please see How to Report a Bug.

imlitimlit

@pesala
You have a good point with firefox being from cache.
Vivaldi runs the page again on the save page action. I confirmed that by running fiddler.
That seems really messed up, considering I may be looking to capture a point in time result, or I just don't want to wait again on a large request to process.

Pathduck

For what it's worth, I got the same result when testing in Chrome/Chromium 100, Edge 100, Opera 86 so this is clearly a Chromium core issue.

But yeah, pretty stupid idea to redo the request instead of just downloading from cache. Blame Chromium devs I guess - that's what we always do

Also there is something wrong with that site, it does not give a correct number for the content-lenght header, this could even be a potential cause of the issue:

$ curl -I "https://transition.fcc.gov/fcc-bin/amq?call=&arn=&state=&city=&freq=530&fre2=1700&type=0&facid=&class=&list=4&ThisTab=Results+to+This+Page%2FTab&dist=&dlat2=&mlat2=&slat2=&NS=N&dlon2=&mlon2=&slon2=&EW=W&size=9"
HTTP/2 200
server: Sun-Java-System-Web-Server/7.0
content-type: text/html
content-length: 25412
expires: Mon, 02 May 2022 20:12:36 GMT
cache-control: max-age=0, no-cache, no-store
pragma: no-cache
date: Mon, 02 May 2022 20:12:36 GMT
strict-transport-security: max-age=31536000 ; includeSubDomains

Actually, come to think of it, by the look of the cache-control, expires and pragma header, it might be that Chromium does the "correct" thing here, as the headers tell the client browser to not cache or store the content at all. Again, stupid, but this one's on the site devs.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control