You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome (not FF and not Safari, they are just fine) was failing when I send a large number (more than 1000 or so) api calls via a fetch array. I thought I could solve this by reducing concurrency using async-pool, but Chrome still fails with code like the following:
In Firefox and Safari, the above code executes without any issues no matter the size of the array, but in Chrome (87.0.xxx at the moment, but many versions) I get a series of failures (Uncaught (in promise) TypeError: Failed to fetch) when the number of fetch calls in the array is large (more than several hundred)
Any clue how I could make chrome work with this?
The text was updated successfully, but these errors were encountered:
Well, chrome has some serious issues that could only be dealt with by introducing a slight delay between each and every individual fetch request, so I had to setTimeout to 5ms, then loop over everyone individually. UGH google.
Chrome (not FF and not Safari, they are just fine) was failing when I send a large number (more than 1000 or so) api calls via a fetch array. I thought I could solve this by reducing concurrency using
async-pool
, but Chrome still fails with code like the following:In Firefox and Safari, the above code executes without any issues no matter the size of the array, but in Chrome (87.0.xxx at the moment, but many versions) I get a series of failures (
Uncaught (in promise) TypeError: Failed to fetch
) when the number of fetch calls in the array is large (more than several hundred)Any clue how I could make chrome work with this?
The text was updated successfully, but these errors were encountered: