-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Website CPU usage #3598
Comments
I haven't heard any complaints, and I have Bootstrap open nearly all day every day in Chrome. No problems on my end. If some others report this, we'll look into it more. |
I see this with Firefox as well. I visit the twitter bootstrap site and within 15 seconds the fans go crazy on my laptop. I go run top -o cpu and see Firefox taking 88-96% cpu. I'm using Firefox on Snow Leopard. |
same. the compiled style.css file has 9500 lines. cpu usage is high throughout. I guess I have to cut some lines. |
its not the size of the css file, its the css3 animations being used most likely. just go load up a empty page with bootstrap js/css loaded. you will see 0 activity in cpu. |
I have same problem in my Bootstrap based website in Chrome and Firefox, is here any way to make it lighter? |
I haven't seen this much. I have seen it at times, but this has been caused by my application more than Bootstrap running. I would leave the profiler running for a little time and see if some methods pop out at you. If you are using MV* type of frameworks with bootstrap, you could be seeing these issues because of the default logic to destroy lingering objects and data. Again, the profiler should help you determine the issue. Lastly, extensions on your browser could cause things like this as well. Try disabling and seeing if you still see the issue. @thezoggy if the animations are not used all through out the page, it should not be a problem. |
I have noticed that if you leave the bootstrap website open for long periods of time in Google Chrome (specifically http://twitter.github.com/bootstrap/components.html#navbar) that it will uses up very large amounts of CPU ~90%.
The text was updated successfully, but these errors were encountered: