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

100% CPU utilization on first run in Firefox and Chrome (HEAD) #497

Open
irskep opened this issue Jan 8, 2017 · 1 comment
Open

100% CPU utilization on first run in Firefox and Chrome (HEAD) #497

irskep opened this issue Jan 8, 2017 · 1 comment

Comments

@irskep
Copy link
Contributor

irskep commented Jan 8, 2017

I set up Groovebasin on a 70 GB library. The first time I opened the page on both Firefox and Chrome, it was kind of responsive but eating a whole CPU. After a while Firefox just stopped responding.

Killing the tabs and reopening them seems okay.

@irskep
Copy link
Contributor Author

irskep commented Jan 8, 2017

Looks like if I open the page just as the library is starting to be built, it works fine and live updates the library as it is populated. After a few dozen albums the page hangs.

If I had to guess, I'd blame it on tons of unnecessary DOM updates per frame.

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

1 participant