Problem with Internet Explorer

Question

I am currently experiencing an intermediate problem with some inherited client-side javascript. Each time, so often, users encounter a browser when the cursor becomes a timer for eggs, and then the browser does not respond.

I had a real difficulty in determining where the problem came from. With the exception of disabling large javascript blocks at a time, is there a way to detect a hang in Internet Explorer and then check the stack trace to determine the last few functions called to localize the problem?

Any help with this would be really appreciated.

Answer 1

. - IE Dev Toolbar Javascript. Fiddler - -.

IE, , Internet Explorer. .

, , Process Explorer Process Monitor. , .. IE.

javascript , firebug.

Answer 2

IE, Firefox , Firefox. , , .

Answer 3

, -, script ? IE8 beta 2 /, (, google, ajax-, ..) . , firebug profiler , , ,

Answer 4

I can repeat the same steps several times and not have an error, but then, apparently by accident, I will make the browser freeze. I guess what I ask is a good strategy to track the error and fix it when I cannot easily reproduce it. I was hoping there was a way to catch the global, i.e. To hang.