Kytetiger Jun 16, 2023 @ 1:53pm
Minified React error #185
I simply clicked on the screenshot manager and this message appeared


"
Something went wrong while displaying this content. Refresh
Error Reference: Shared SteamUI_8129386_f385dbfebf120acd
Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
"

following the link, the info shown is:

"
The full text of the error you just encountered is:
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
"


🤷
< >
Showing 1-15 of 18 comments
RiO Jun 16, 2023 @ 2:04pm 
It means someone working on the new ReactJS-based UI components that build the UI for the new Chromium-all-the-way-down Desktop UI, made a screw-up.

ReactJS is a development toolkit for UI components that's based on reactive state.
That is: if X changes its value, then 'do something' where X is being consumed.
That can be in a bit of UI that is meant to render X's value.
That could also be in a derived property for instance Y = 2 * X, which computes a new value for Y, so that Y changes, so that you have to 'do something' wherever Y is being consumed.

Problems start if you made a mess of your application architecture to the point that that dependency graph has cycles in it.

Because at that point an update to X can flow in never-ending circles.
As a precaution, as soon as an update cycle starts, React starts bookkeeping the depth of the update, i.e. the length of the chain of dependency hops. And as soon as that goes too deep, it bails.

It's kind of crude, but it works. (A better way would be a mark-and-sweep algorithm that cycle-breaks when a dependency relationship that was already traversed earlier, ends up wanting to traverse again. But it's also more expensive to book keep. So the trade off is to just do it the crude but low-resource way.)


There's nothing you can do here to stop this from happening.
Other than opening a bug report for it on the Steam beta forums (which do in fact take reports for the stable client as well) and then waiting it out.

Last edited by RiO; Jun 16, 2023 @ 2:06pm
xerbly Jun 18, 2023 @ 12:38pm 
I have the same issue.. what the hell
L0NGH0ST_ Jun 19, 2023 @ 10:49am 
+1, worst on stable than beta

Occrurs mostly on Download tab
Seven of Ten Jun 28, 2023 @ 11:05am 
I have also been having this issue over the past week. Finally got around to looking into it because it's so freaking annoying.
DaftCanuck Jun 29, 2023 @ 4:32am 
Just ran in to this issue on the downloads tab. Fantastic work Steam devs.
Cuddle Cactus Jun 29, 2023 @ 9:56am 
I just got it as well, whenever I hover over stuff in downloads to X it to be unscheduled.
orbrover Jul 8, 2023 @ 2:31pm 
+1

Edit: It eventually fixed itself. 25Aug2023
Last edited by orbrover; Aug 25, 2023 @ 6:41pm
Pizzaman Aug 25, 2023 @ 4:50am 
This problem still exists. Are the devs even working on this?
rogermorse Aug 27, 2023 @ 4:10am 
same for me
Pizzaman Sep 3, 2023 @ 7:20am 
The Problem is STILL NOT FIXED.

Reading this and the amount of people affected by it ... you wouldn't believe, if someone told you that this is one of the biggest Game Platforms in the world.
naz239 Sep 16, 2023 @ 1:55pm 
not fixed. It is very common on developer sale page doing mouseover on some games.
Still unfixed, I get this while trying to scroll in the screenshot manager (I take a lot of screenshots)

Someone please reply to me in the future f there is a fix
naz239 Sep 24, 2023 @ 5:56am 
More or less fixed deleting all info cookies, etc for steam but its boring do it, relogin etc
Pizzaman Oct 19, 2023 @ 11:47am 
Aaaaaaand it's still not fixed.

Something went wrong while displaying this content. Refresh
Error Reference: Shared SteamUI_8382890_851941a32bb71850
Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Last edited by Pizzaman; Oct 19, 2023 @ 11:48am
DarkXiomax Nov 2, 2023 @ 3:46pm 
If you happen to be on a chromium based browser, such as Google Chrome, Brave, etc:
1. Go to chrome://flags/#fingerprinting-client-rects-noise in the url bar
2. Make sure it is turned off / disabled
3. Relaunch browser, this should fix it.
< >
Showing 1-15 of 18 comments
Per page: 1530 50