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
When visiting gigantti.fi with esr91, the page looks to be working first, but soon displays a "something went wrong" type of message. At this point the browser starts eating memory, some 30MB/s. The browser process doesn't close with a swipe, but requires a SIGKILL to go down, or an oom killer to snipe it. This is what gets written in console:
JavaScript warning: https://www.gigantti.fi/zKMfsN/LTkgA_/V4y/mWE/mM91Qw/5YiJkQ6S4mXb/XkczNCdR/VhR1TA/4bCx4, line 1: unreachable code after return statement
JavaScript error: https://www.gigantti.fi/_next/static/chunks/fd9d1056-914b8c2a9cccdd42.js?dpl=dpl_8p8YG9CCzKZM4aUKyfhM8aqJLHu4, line 1: Error: Minified React error #185; visit https://react.dev/errors/185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
JavaScript error: https://www.gigantti.fi/_next/static/chunks/fd9d1056-914b8c2a9cccdd42.js?dpl=dpl_8p8YG9CCzKZM4aUKyfhM8aqJLHu4, line 1: Error: Minified React error #327; visit https://react.dev/errors/327 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
JavaScript error: https://www.gigantti.fi/_next/static/chunks/fd9d1056-914b8c2a9cccdd42.js?dpl=dpl_8p8YG9CCzKZM4aUKyfhM8aqJLHu4, line 1: Error: Minified React error #327; visit https://react.dev/errors/327 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
The first React error link expands to 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. No clue if that's the cause though.
Changing the user agent to the one commonly used doesn't change the behavior.
This affects esr78 as well.
The text was updated successfully, but these errors were encountered:
When visiting
gigantti.fi
with esr91, the page looks to be working first, but soon displays a "something went wrong" type of message. At this point the browser starts eating memory, some 30MB/s. The browser process doesn't close with a swipe, but requires a SIGKILL to go down, or an oom killer to snipe it. This is what gets written in console:The first React error link expands to
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.
No clue if that's the cause though.Changing the user agent to the one commonly used doesn't change the behavior.
This affects esr78 as well.
The text was updated successfully, but these errors were encountered: