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

Webpage using insane amount of CPU, running at ~1 FPS #40

Open
angeld23 opened this issue Apr 26, 2024 · 4 comments
Open

Webpage using insane amount of CPU, running at ~1 FPS #40

angeld23 opened this issue Apr 26, 2024 · 4 comments

Comments

@angeld23
Copy link

Usually, Chrome sits comfortably below 10% CPU, but it spikes to over 50% when I have the website open. The page is extremely laggy and slow. I definitely don't remember this happening the last time I used it.

image

@angeld23
Copy link
Author

Runs fine on Firefox. Chrome profiler is saying that the long frame times are from something called "Commit" that it won't give any more information about.

@Krafpy
Copy link
Owner

Krafpy commented Apr 26, 2024

Hi! Do you have a way to reproduce this behavior? I tried a few solar systems and trajectory settings, and CPU usage stays around 10% on Chrome for me.

@angeld23
Copy link
Author

Hi! Do you have a way to reproduce this behavior? I tried a few solar systems and trajectory settings, and CPU usage stays around 10% on Chrome for me.

Not sure. My Chrome is fully updated and this happens in Incognito too (so not an extension causing this). Weird.

@Krafpy
Copy link
Owner

Krafpy commented Apr 29, 2024

I tried again on another computer and I don't seem to find a way to reproduce this behavior.

What operating system/version are you running on? Which chrome version? Does it happen on other Chromium based browsers?
Does it happen immediatly once you open the page or after some actions?
Can you date back roughly when this issue first happened?

I suppose that the "Commit" process you pointed out corresponds to the one related to Chromium's rendering architecture.
My first hypothesis would be that some javascript ends up in a state where it constantly tries to update the DOM.

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