![]() ![]() This doesn't help with IE's slow script dialog logic, which is based on the number of statements (not time) that were executed. None of these profilers tell you how many statements of code within a function were executed during profiling they tell you only how long was spent in the function and how many times the function was called. ![]() IE's profiler will also give you a count of how often a function is called. To this end, the profilers available in (or as add ons) to the browsers can identify the percentage and usually raw time spent executing a function, both inclusively and exclusively for a function, and the results can be sorted accordingly. With the exception of IE, other browsers decide a script is long running not based on the numbers of statements executed but rather the amount of time the script spent executing. Most browsers, including IE8 and later, have profiling tools that enable the developer to determine JavaScript CPU usage. The question is, how to determine what area(s) of the code are causing the dialog to appear for a specific user? Often this problem occurs with a very large code base (including third party libraries), so a manual review of the code base without some tooling support is not feasible. So, I understand what the problem is in general terms, and I understand what the options are to solve the problem, again in general terms. This is a legitimate strategy across all browsers.
0 Comments
Leave a Reply. |