Thank you for the additional information. I think I better understand the problem. It's happening when our framework is trying to build the FrameInfo object as part of test execution, correct? To investigate why this is happening I need a way to reproduce it. is there a publicly accessible URL we can connect to that will demonstrate this problem (and what are the instructions for getting to the problematic frame)? Alternatively can you capture a Fiddler trace of the problem page and send it to us? We can use the Fiddler trace to simulate your web server and use it to reproduce the problem. If you concerned about privacy you can email the file to firstname.lastname@example.org and reference ticket 685161. Then it will be directed to me to continue our investigation.
All the best,
the Telerik team