Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser uses more and more RAM in Gigantti website #1073

Open
direc85 opened this issue Aug 31, 2024 · 1 comment
Open

Browser uses more and more RAM in Gigantti website #1073

direc85 opened this issue Aug 31, 2024 · 1 comment

Comments

@direc85
Copy link

direc85 commented Aug 31, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@direc85 and others