In our MS Dynamics CRM 2013 SP1 instance, when certain contact records are viewed in the contact screen, a few seconds after the page loads the browser suddenly spikes a CPU core to 100% and freezes. The browser remains unresponsive until it is closed forcefully on some computers, but on computers with more memory the situation resolves after about 3 minutes, then a few seconds later the cycle repeats and the browser hangs again. The freeze only happens on certain contact records, and does not happen at all on other contact records, but it is always consistent for a given contact record in that it either happens, or doesn't happen, for that contact. I'm using IE9.
I've tried using Fiddler, and the F12 developer tools in IE to track it down, and I can see some evidence that the problem is not waiting for network/server requests though I'm not positive, but appears to be JavaScript on the client that is not waiting for any kind of asynchronous request. Unfortunately, due to the minification and abstract nature of the JS on the contact form, I can't make heads or tails of the code.
I've tried correlating aspects of the contacts where the problem occurs, and differentiating with aspects of contacts where the problem does not occur, but I can't find anything that correlates 100%. In other words, I can't find any value or set of contact field values that consistently cause the browser to freeze.
I have noticed on at least one of the contact records that the activities list/grid does not display until the 3 minute situation is over.
What tools or techniques are best for finding the root cause of this issue?
