can't open certain pages due to "loading chunk 4970 failed" error

[fran]

it's been happening for a few days now and i don't know if it's something on my end or there's anything i can do to fix that

reloading the page clearly doesn't do anything

any help / feedback would be appreciated . thanks

[Crystal Sharrd]

Originalmente postado por SHIFTY-T3RROR:

Ive been getting this error now for the past few days since the events etc just wont load with that error msg only way i can get it to work is on pc otherwise my IOS is fkd :/ im not sure anymore. :trolol:

I'm having the opposite issue, I can access things just fine in the Android app, but I run into the error all the time on PC.

[fran]

it probably won't make a difference but i'll contact support tomorrow about this and mention this thread and that other people are having the same issue

feel free to do the same , maybe they will look into it if enough people mention this problem

[Lolo]

I can't get free stickers because of that :/

[Tharon]

Happening to me, but on Steam, probably because i'm using an old version of the client based on an old chromium.

I can only speculate about it, but i think that Akamai (the content delivery) is rejecting some connection made by a not updated chromium.

@Crystal Sharrd
Are you using an old Steam client too ?

[若叶睦]

hi bro，maybe you could download steam client again，i have sloved this problem after i delete steam client and download it again

[fran]

yes,it's definitely an older steam client / chromium issue

[Dura_Ace]

Originalmente postado por Tharon:

Happening to me, but on Steam, probably because i'm using an old version of the client based on an old chromium.

I can only speculate about it, but i think that Akamai (the content delivery) is rejecting some connection made by a not updated chromium.

@Crystal Sharrd
Are you using an old Steam client too ?

Something went wrong while checking for a Steam Client update.

Looks like i am current or cant get to current due to an error. At least once while using steam i had to totally install steam again from fresh as it would not update. I wil wait a while for that as it is workign for now and catn be bothered to do all that wen it does appear to be not on my end.

Assets are failing to be called. This is most likely on their rend.

[Thinkpad4]

Is it possible to update the CEF browser without updating the client? Maybe a unofficial patch or something? Thank you very much

[Cray]

I seem to recall having this issue as well.

As in, that is what I recall. It's hard to remember precisely, because this entire crapload of an app is so chock full of bugs it's just amazing.

garbage, just plain garbage, the entire app. gets worse with every update. had to wipe and reinstall three times this week because steam gets stuck in a crash loop and won't even start properly.

took me a full minute of watching steam endlessly reload a black page to get onto the forums to see if others were having the issue i was having - it won't even launch my games.

seriously, i can't even play my games because steam just flat out fails to load them, and on the occasion i do get them launched, which is random, the overlay crashes immediately and tabs out to desktop to open the steam main window.

and then the main window crashes. then steamwebhelper dies.
then steam says "exiting steam" forever, but does not exit.

sorry, i just had to throw that in there too, since it's relevant on the more general issue we're all having:

steam is a complete piece of ♥♥♥♥, basically useless. if you're among the few who happen to be on the same platform and general hardware as the devs, you're lucky and it works, otherwise you're among the thousands who sit on systems they failed because they don't test anything before updating.

♥♥♥♥♥♥♥ this app is such a collossal failure, i'm running out of insults to throw at it.

edit: ps, not a single other application or program is having any issues on my system. only steam.

[RiO]

This has nothing to do with how old your browser is or which browser you are using.
Chunks are terminology used by Webpack, a build pipeline and bundler tool for JavaScript.

https://webpack.js.org/concepts/under-the-hood/#chunks

A 'chunk' is basically a part of a JavaScript application that Webpack has shoved into one of several actual files, which may combine several modules. It doesn't load everything into one huge file, because using several means they can be downloaded in parallel - which is faster. (And in some cases, they can be loaded later, on-demand - only when needed.)

What people are seeing now with chunks failing to load is very likely simple network failure, because Steam's backend is under heavy load during the Summer Sale - and after close to 2 decades of each year having the same thing, they still haven't learned to scale out their capacity properly in advance.

If their solution is poorly load-balanced, then your requests may end up being routed to servers that are already overloaded, and only occasionally find their way to a server that isn't croaking under pressure. Similarly, if they use a deterministic way of balancing requests (such as every Nth request from the same IP goes to the Nth server in a set) then it will likely always be the same network request for the same file that is failing.

If these are supposed to be cached static assets served via Akamai, then perhaps there's another cache misconfiguration issue again, which is either causing stale store pages to refer to JS files that no longer exist, or is causing up-to-date store pages to not be able to find JS files that haven't propagated into Akamai's CDN properly, which - given that Akamai is also load balanced and is geo-distributed (like any good CDN) - will also give different results for different people, and different results over time.

[Tharon]

Sorry RiO, i think you are wrong this time.

In my system i have the error in Steam and no error with my browser and again no error if using an updated Steam in a Windows 10 VM.

So i have different results with the same IP, same PC and at the same time. The only difference is the Chromium version because my Steam client is from DEC 2022.

(oh... and this is started a couple of days before the sale, just after the latest maintenance)

[RiO]

Originalmente postado por Tharon:

Sorry RiO, i think you are wrong this time.

In my system i have the error in Steam and no error with my browser and again no error if using an updated Steam in a Windows 10 VM.

So i have different results with the same IP, same PC and at the same time. The only difference is the Chromium version because my Steam client is from DEC 2022.

(oh... and this is started a couple of days before the sale, just after the latest maintenance)

Then something screwy is happening.
The error message given here is what Webpack throws when a chunk fails to load.
That can be for whatever reason, including network error. (It usually is network error due to misconfigured output paths, but then it would fail for literally everyone - so it's not that here.)

If it fails to load because of something that's not network error, e.g. because of a failure to parse the script or because a piece of the script failed to actually execute correctly, then there should be an additional error reported just before this one.

Has anyone affected seen anything like that?

[Crystal Sharrd]

Originalmente postado por Tharon:

Happening to me, but on Steam, probably because i'm using an old version of the client based on an old chromium.

I can only speculate about it, but i think that Akamai (the content delivery) is rejecting some connection made by a not updated chromium.

@Crystal Sharrd
Are you using an old Steam client too ?

Yes, due to severe downgrades with the new client that make it undesirable. Notably the lack of support for custom themes (and the new client is an eyesore), as well as higher memory usage.

[kameron]

welp went to buy another game and cant even look at store, guarnteed im not alone and steam is losing sales every day this issue is up so theyll prolly fix soon.

[fran]

so,question,are we all using older version of the steam client and / or older operating systems or steam mobile app ?

in other words,anyone with the latest version of the steam client on win 10/11 or app with this issue ?

if no,like i suspect,then we know why we're suffering