Profiling Scripts in Internet Explorer 8 and Later

Applies to AQTime 8.81, last modified on January 18, 2022

The recent versions of the Microsoft Internet Explorer browser introduced a number of enhancements. They differ significantly from earlier versions of the browser. Since version 8, the internal structure of the browser has also been modified (for example, a separate iexplore.exe process is created for each new tab). To reflect these changes, AQTime has a special script profiling mode that is optimized for Internet Explorer 8 and later. This mode allows you to obtain profiling results faster and does not require that the Microsoft Script Debugger component be installed.

The mode activates automatically when AQTime determines that the host process is Internet Explorer 8 and later. This mode is available for all three ways of script profiling (via the host application, via a script file or via a URL).

Note: In order to obtain the correct results when profiling in Internet Explorer 8 mode, close all Internet Explorer windows before you start profiling. Do not open pages and windows until profiling is over.

Internet Explorer 8 mode has the following specifics:

  • JScript only profiling - Internet Explorer provides AQTime with profiling results only for JScript code. VBScript scripts are executed by the browser but they are not profiled.

  • Routine level profiling - Profiling is performed at the routine level only, line level profiling is not supported. Yet, since the version of the host process cannot be determined prior to launching it, the Line Level radio button is still enabled in the Code to Profile pane.

  • Verbose results - Profiling results include data for routines contained on web pages or in module files, data for object method calls, and data for helper service routines of the browser.

  • Extended data structure names - Routines and other data structures are named according to the internal notation of Internet Explorer. So, in profiling results, you may encounter items like "Main, JScript - window script block", and other items that have extended descriptions. If a routine does not have a custom name (many helper routines have no name), then it is entitled using the following pattern: "Routine Id: rID; Script Id: sID; Routine name: Unknown", where rID and sID stand for routine and script identifiers, respectively.

See Also

Profiling Scripts
Profiling Scripts - Troubleshooting

Highlight search results