In Internet Explorer on the Desktop, by default, Content Processes remain at 32bit by default for compatibility with 32bit ActiveX controls, Toolbars, BHOs, etc. If you manually invoke C:\Program Files (x86)\Internet Explorer\iexplore.exe, that 32bit process will simply launch the 64bit version of iexplore.exe (with the appropriate command line parameters) before exiting. In support of this change, the various registry points that point to Internet Explorer have been updated to point to C:\Program Files\Internet Explorer\iexplore.exe. Even toolbars, which visually appear as if they’re in the Manager Process, really run down in a Content Process.įor IE10, we’ve changed IE such that Manager Processes always run as 64bit processes when running on a 64bit processor running a 64bit version of Windows. All HTML content and ActiveX controls run in the Content Process. You need to read the Understanding Enhanced Protected Mode article to understand Internet Explorer’s Process Model and Bitness:įor the past several releases, Internet Explorer has sported a multi-process architecture, where the “ Frame” or “ Manager” process runs at Medium Integrity and the “ Tab” or “ Content” processes run at either Low Integrity (Protected Mode) or Medium Integrity (for Zones where Protected Mode is disabled, like Intranet sites).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |