Run chrome canary, http://tools.google.com/dlpage/chromesxs, or the use the dev channel. Then use then use speed tracer, https://developers.google.com/web-toolkit/speedtracer/, to find your bottle neck. It sounds like you are getting stuck in a loop that is hogging the UI thread.
On Mon, Apr 23, 2012 at 5:53 PM, Rajiv Jivan <[email protected]> wrote: > I don't have a lot of Javascript and when it becomes unresponsive at > that point even changing the url in the address bar doesn't help. I > have to close to tab. This obviously isn't enough for you to help > with. Any suggestions on how to capture additional data that might > provide a hint. > > On Apr 23, 1:10 pm, John Roberts <[email protected]> wrote: >> Chrome, in general, is a memory hog. I tend to notice it more on >> javascript intensive sites (like google groups) than on CSS intensive >> sites... >> >> >> >> >> >> >> >> On Saturday, April 21, 2012 6:36:39 AM UTC-7, Rajiv Jivan wrote: >> >> > I've noticed that occasionally Chrome browser becomes unresponsive >> > when using Bootstrap. I believe its related to the use of Stateful >> > buttons. Once I click it, the browser stops resonding and nothing on >> > that page works. It can't be reproduced consistently. Has any one else >> > noticed this?
