Internet Explorer @ IETF 90

This week Microsoft is sending a number of engineers, including members from the IE team, to the Internet Engineering Task Force meetings in Toronto. We’re looking forward to the conversations and working groups as it’s always great to get together face-to-face with engineers from across the industry.

In particular, there are several discussions we’re excited about including HTTP/2.0 and the safe preference header Internet proposal, which we’ve already been working on with several industry partners and has been enabled in IE as an early implementation.

If any of you are attending the event, please stop by and say hello.

-Adrian Bateman

Comments (34)
  1. Wes says:

    Javascript2 or a successor to javascript is most needed at this time; including the minimal level of 1970s era programming Pascal level features modules, typed parameters, typed variables, structs, nested methods is best.

    The last 19 years have been good for JavaScript; so now we need core proven programming technologies.  The implicit typing and void pointer level coercion should not be today's problem – that was a 1970s and 1980s problem.

    Typescript, coffee script and other cross compilers are only a stop gap and not a long term solution.

  2. __hAl__ says:

    When will new IE12 version be released?

    Microsoft again is already behind schedule for one major browser version every year which should be an easy target.

  3. adrianba [MSFT] says:

    @__hAl__: IE11 has been updated multiple times with new functionality. There was a large update in April (see…/announcing-an-updated-version-of-internet-explorer-11-available-on-windows-8-1-windows-7-and-windows-phone-8-1.aspx) including Enterprise Mode, WebGL updates, and new F12 tools. Two weeks ago we included the safe preference header implementation described above in the July update. These are just two examples since General Availability of IE11.

  4. sylviane gomez says:


  5. Yannick says:

    @adrianba – Which is great, through it would be very handy if you guys would post a page somewhere that discribed what changed in each version of IE11. I know for example that 11.0.9 added Improved support for vertical text, but a full list for each version would be great. What else would be great is if you could tell us if the changes in the Internet Explorer Developer Channel are coming to IE11 or that it is actualy a new build for IE12. And when we will see IEDC 2 would be nice to know too!

  6. James S says:

    Whenever there are actually feature updates (and not just security and other fixes), it would be nice to see branded updates to the browser, like 11.1, 11.2, etc.  Each should be accompanied by a changelog.

    This would help a lot in testing, so when a feature we depend on changes we know when it happens, what changed, and what we need to test.  Similarly, having really simple branding changes (e.g. an "11.1") would make it easier for us to communicate to our own customers.  For example, if we use feature detection to tell whether a capability exists or not, we might be able to tell our customer "if you want capability X in our software, please upgrade to version 11.whatever".

  7. Yannick says:

    @James S – Indeed, the second number in the IE version should be there for a reason, and ever since IE5, it Always has been 0. Internet Eplorer 11.0.7 should have been named 11.1. Sure, "it's just a number", but it makes things so much clearer to end users. A nice changelog, like I said before, would come in handy for developers too. I'm not sure if you guys are planning to update IE with Windows 8.1 Update 2, but please go for a normal versioning. Not like Chrome and Firefox do, just the old school features = minor bump.

  8. adrianba [MSFT] says:

    We definitely appreciate the feedback and have been discussing the best way to highlight these changes. In general, changes are published in the Microsoft Knowledgebase including non-security changes. For example, here is the article for July:…/2975687

    On the question of when features will move from the Developer Channel to IE: this will depend on the size, impact, complexity, and independence of the feature. For example, small independent changes that are additive and do not impact other features are more likely to come sooner than things that require more code churn or greater changes to the engine. We decide for each feature when it might be ready to ship as we make progress. We'll talk more about this soon – watch this space.

    Thanks again for the input.

  9. Maxim-064044 says:

    Will the final version of IE12 all also support Windows 7 SP1? We would like to!

  10. Mike says:

    Engineers in Toronto! Interesting.

    What about those engineers who reported over 1 million bugs on Microsoft Connect, which you guys never cared to take a look again for ages now? Fifth year now and I got the same BS low-priority excuse! Is low-priority bug (even through its effecting millions out there) has any deadline? 10 years? That's a real shame!

    Changing platforms will not do any good. Its just another eyewash. The fact remains; Internet Explorer guys don't love their job.

    Fix the GODDAMENED OLD bugs and earn some respect! Use the sort button on Microsoft Connect and start with the oldest.

  11. pmbAustin says:

    I posted this to connect about the white-tab/flashing-tab/rendering issues with extended use, as one or more iexplore.exe processes grows large, and performance nose-dives and functionality starts breaking…  we'll see if anyone actually looks at it.…/white-tabs-when-iexplore-exe-process-gets-large-rendering-problems

    It's ridiculous though… the other day I had this happen FIVE TIMES across two different PCs.  In one day.  Never a week goes by that this doesn't happen.  Different boxes (desktops, laptops), but all on Windows 8 (it happened in 7 too), and IE11 (it happened in 10 and 9 too).  It's been around forever.

    I have no idea how non-technical people deal with it or even perceive it… they probably just switch browsers to one that "works".  Me, I just kill the rogue process and things return to normal, but that's still annoying.

  12. Real McCoy says:

    @pmbAustin, up-voted! Hopefully that will make an impact?

    The tab browsing is broken in so many ways, I don't know how come 100,000 employees at Microsoft miss it every day!

    Here is my story:…/javascript-arrays-length-retrieving-is-really-slow-implementation-seems-like-against-the-specs…/no-drop-shadow-when-printing-svg…/wrong-inheritance-with-svgs-fill-opacity…/ie-amnesia-forgets-all-user-preferences

    Those are the issues with "tangible" reproduction steps.

    Besides that, there is a crazy bug since ever I have been noticing in Internet Explorer. It happens intermittently but it does happen on ALL IE version on ALL versions of Windows server/client:

    "When the page is refreshed, it shows Page Not Found because the address bar changes the URL's protocol to http://http//.."

    Notice an extra http// (without colon) after the actual protocol? It gets appended automagically!! Removing that and pressing enter loads the page correctly.

    Now, in my educated experience, somewhere in IE code, there is this http// string without colon, which need to be changed with its correct variant http:// (with colon). How long should it take to fix that string? Hmmm.. And I am observing this at least since IE7..

    Giving their track record on fixing bugs, I am pretty sure this kind of annoying issues will persist in IE20 as well.

    This is the kind of a reason, people who hate IE can't exactly explain why they hate it. They just hate it because of the "user experience" which fends them away. Doesn't matter if it supports all web technologies known to man kind. They are still riding their high horses thinking they are doing the "right thing".

    Without getting indulged "with" the community and fine-tune every aspect of this whale, they are just losing user-base.

  13. Steve says:

    It has been a bit since it launched but I can't seem to install the dev preview release of ~IE12~ on a Win8.1 64bit PC.

    I get the following errors on every attempt:

    [1478:1470][2014-07-25T20:21:17]e000: Error 0x80070643: Failed to install MSI package.

    [1478:1470][2014-07-25T20:21:17]e000: Error 0x80070643: Failed to execute MSI package.

    [0FF0:0FF8][2014-07-25T20:21:17]e000: Error 0x80070643: Failed to configure per-machine MSI package.

    [0FF0:0FF8][2014-07-25T20:21:17]e000: Error 0x80070643: Failed to execute MSI package.

    The help link in the error dialog is also not clickable (nice touch MSFT!)

    Is this a known issue?

    PS I have full admin rights and even tried running the setup as the administrator.

  14. Steve says:

    the help link:

    is not helpful at all. I've rebooted multiple times and all my .Net and PowerShell utilities are fully up to date.

    Can the error messages be a bit more cryptic? I know that Microsoft doesn't like to give error messages that are actually helpful but for developers you really should try to make this work better.

    It's very frustrating.

  15. Jason says:

    @Mike – totally agree!  I spent hours filing bugs on connect but in the end gave up.  with every new release they marked all the open bugs as wontfix or worse yet "as designed" (e.g. they didn't implement it or messed it up when they did it).  Sadly while dealing with that frustration Microsoft would then shut down the previous release tracking and remove all bugs.

    100's of us complained and as always it fell on deaf ears.  After dealing with this for 2, then 3 releases we realized that we had no interest in playing this game anymore and there was a massive revolt against filing bugs in Connect for IE until Microsoft started to respect the developers that were filing them.

    Sadly that day has yet to happen.  As a result Connect is now an abandoned wasteland not used any more and utterly rejected by most developers.

    Its very sad.  Chris Wilson and Eric Lawrence were the only IE Team members that realized proper fully open bug tracking was the only correct solution going forward to get the respect of developers back and make this a full circle effort to get IE caught up to other browsers.

    Microsoft/IE MGMT never got on board.  Chris and Eric left for better pursuits not under the constraints of Microsoft's old ways – and here we are today – still without proper bug tracking and terrible animosity due to the mismanagement and failings from the past.

    A public apology for the behavior  was requested (still not yet received).  Once provided with a written commitment to actually listen to feedback, act on it, verify bugs, and allow submission of test cases that other developers can verify then I'm sure we'll all come back to help.

    For now – we couldn't care less…. because Microsoft doesn't care at all.

  16. Patrick says:

    I agree with most of commentators here. Ignoring, playing hide-and-seek and ducking the issues will not do any good to IE rep.

    Internet Explorer (E) is a brand. You guys are responsible for this brand. You guys are paid for Microsoft to keep up to the consumers' expectation of this brand. I as a hobbyist closed over 300 issues in last quarters for Microsoft open products on GitHub for free of cost. You must not be liking your job, that's why IE users and developers are also so dissatisfied, even after tons of improvements. Too much for nothing?!?

    The wrong protocol issue that "Real McCoy" has raised, I have also experienced it on couple of occasions. There is a similar issue that happen when IE frame crash, the address in the URL is appended with something like "res://ieframe.dll/acr_error.htm" and the tab forgets its back/forward button history! That issue is also present in IE since v7 (ever since tab-browsing was introduced). If you search on Google or Bing, it will flood the result page. But that is not least of your worries, right?

    I also agree that UX is a key to win hearts back. And believe it or not; besides those issues, IE's UX sucks. Quick Tabs are removed from IE11, which shows how committed you are to murder every cool prospective aspect of the browser. People were asking for per-tab volume control in that quick-tab view and suddenly it disappeared altogether. Nice!

    These are the small things which make difference. Throw couple of "absolutely" useful features (not necessarily unique but be creative by carefully reading our feedback), throw some quick releases to the mix and see people getting happier. Keep being stubborn and keep losing until you lose it all.

  17. NumbStill says:

    @Real McCoy –

    The http://http/ thing is usually a result of prepending the protocol (or scheme) to the URL.

    http:// will be automatically corrected to http://http// by all of the browsers.

    So I do not think anyone is injecting "http://" to the URL, instead the protocol is prepended twice.

    I expect an HTTPS URL (when the issue occurs) to turn into https:// and be corrected to https://https//

  18. pmbAustin says:

    I filed the bug, added comments with additional "how to try and reproduce", and not even an acknowledgement (most other reports at least get an acknowledgement).

    For a bug as serious and as annoying as this one, MS seems to want to just ignore it.  No feedback at all, not even any questions about it.

    And that Connect form is horrible… is there some way to better filter the list or search for things?  If so, I can't find it.

  19. NumbStill says:

    @pmbAustin –

    You might want to post a link to the ignored bug here – it may help triage it quicker.

  20. __hAl__ says:

    @adrianba [MSFT]

    A new IE version 12 is needed with support voor HEVC still image profile en preferbly also with support for HEVC/h.265 video.

    The IE version supporting those images needs to become active on Windows 7 (thus before end of mainstream support) as we do not want a situation where we have to keep old format (jpeg) images for too long next to new format images.

  21. pmbAustin says:

    @NumbStill … I did, up above, but I'll repost it again here:…/white-tabs-when-iexplore-exe-process-gets-large-rendering-problems


  22. Gérard Talbot says:


    Does that problem occur when visiting sites that are not (as you describe) "infinite scrolling" ones?

    Do you have "smooth scrolling" enabled?

    "Many tabs are in javascript heavy sites (and maybe some ad-heavy sites) that scroll endlessly.": ad-heavy and javascript-heavy sites will cause problems to any or all web browsers.

    It looks to me like your PC visits sites that require and hog system resources (mostly RAM memory) and then hard-disk (virtual memory) swapping is needed; thus, CPU activity %tage increases as well. The workaround is to avoid badly designed websites that abuse user system resources.


  23. pmbAustin says:

    No, that's not the problem.  I'm just citing ways to accelerate triggering the problem.

    I've had the problem trigger with iexplore.exe sizes of only 400K or so.  The problem is that the process enters an infinite loop.  The page stops rendering completely (going white if you have hardware acceleration on), and the process sucks up 25% of the CPU indefinitely, until killed.

    The problem happens no matter what sites you visit.  It just takes longer.  I never close my browser and only reboot to install updates.  So even sitting with innocuous pages, it can happen.  But MOST pages do use a lot of images and javascript and such…, tech sites, news sites, etc.  

    And the fact that the browser itself slows down more and more the larger the iexplore.exe process gets (regardless of the page size or what site you're on) is a huge clue as well.  And the fact that it can start affecting the system as a whole ("leaking" outside of the tab or the browser) is pretty serious.  Almost any time I notice that my system is behaving weirdly (clicks not registering, icons or other graphics not rendering, serious lag or slowness), if I look at Task Manager, sure enough, there's a very large iexplore.exe process… and killing it fixes the problem.

    This is an Internet Explorer bug.  It's been getting steadily worse since I first experienced it in IE9.  I can reproduce it on vastly different hardware, on completely different networks.  NEVER a week goes by that I'm not affected by this problem, and it can frequently hit me several times a day.

  24. Gérard Talbot says:


    Is the problems still occuring when using latest version of IE11? (currently latest is IE11.0.10 version)

    Are you using the 64-bit version of Internet Explorer?

    If so, do you have

    Internet Options > Advanced and "Enable Enhanced Protected Mode" and "Enable 64-bit processes for enhanced protected mode" checkboxes checked?

    You should provide these infos in…/white-tabs-when-iexplore-exe-process-gets-large-rendering-problems

    General comment on your bug report:

    – you have provided a lot of description, generally useful description but maybe too much (or not enough focused): I still would not be able to reproduce the bug. Your description should focus on only 1 rendering issue (say, tab switching or thumbnail preview), not several rendering issues; otherwise, this makes your description difficult to follow and eventually difficult to reproduce.

    – In a bug report, you should remain formal (as formal as possible at all times), descriptive, as factual as possible and try to be helpful by providing information that is likely to be considered helpful by bug triagers and IE developers. So, clear and objective information is helpful. "Big", "slow", "grows more", "over time", etc.. is less useful (because subjective) than "25% of CPU", "700,000k-800,000k range", "120 seconds" kind of info and type of info.

    – You wrote

    "The expected behavior is that performance doesn't sharply degrade over time, and that rendering doesn't slow down or stop, and iexplore.exe processes don't grow without bound, or get in a loop consuming 25% of CPU while failing to render a page."

    Realistically speaking, this is not sound, not okay. Some websites are so badly designed (javascript-abusive and ad-abusive as you rightly pointed out) that they will hog and abuse user system resources. You know, some roads are so bumpy, broken (unmaintained), dangerous in some cities/countries that even a brand new 2014 car is not assured of not experiencing problems when using those roads.


  25. Gérard Talbot says:

    > No, that's not the problem. I'm just citing ways to accelerate triggering the problem.

    Huh… so, if I understand you, you are saying that "infinite scrolling" sites accelerate triggering of the problem. Did I get this right?

    > The problem happens no matter what sites you visit.  It just takes longer.

    That's possible, that's a possibility … but again, you should let IE developers reach for themselves and by themselves such conclusion. As a bug reporter, you should just remain factual and formal.

    > This is an Internet Explorer bug.

    This is your opinion and it's not really useful in a bug report. A badly designed webpage (ad-intensive, script intensive, image fetching intensive, etc) can abuse user system resources (CPU, memory) and create some or all of the symptoms you describe in other non-IE browsers. IE11 introduced prefetching and prerender features; who knows if these are features already abused by sites developers.

    >  It's been getting steadily worse since I first experienced it in IE9.

    Bug 926585 was created only 1 week ago!

    Opened: 7/22/2014 9:59:11 AM…/white-tabs-when-iexplore-exe-process-gets-large-rendering-problems

    No answer from you regarding "smooth scrolling" enabled.

    One favor to ask you:

    Load in 2 tabs (no other tabs opened) these…/InfiniteLoopIE7.html


    and then scroll up and down those webpages, then resize the viewport, try with smooth scrolling enabled, try with "Enable Enhanced Protected Mode" and "Enable 64-bit processes for enhanced protected mode" checkboxes checked (assuming you use 64-bit version of Internet Explorer 11.0.10). Can you reproduce any of the symptoms you described in your bug 926585 report? … and if so, can you enumerate the exact steps that reproduce such symptom(s)?

    Those test-webpages were proven to create incremental reflow problems; I wonder if those hang bugs were correctly and adequately fixed…


  26. Gérard Talbot says:



    @pmbAustin, believe it or not that infinitely scrolling page is INSANELY huge and heavy, with multiple instances of flash players! It brings any browser to its knees. Try on latest FF, it fails


    So, you were already told what I've been telling you. Nevertheless, there may still be inadequate memory management in IE11.0.10 or infinite reflow or some real bug worth fixing: this is where you should try to improve your bug description (steps to reproduce) and leave it to IE developers to assess.

    Not too long ago, some people were complaining about IE8's limitations of 32 embedded style sheets: I never thought this was a genuine, real and serious bug .. but only some limitation that I personally thought was very reasonable IMO.

    The problem I see with your bug report is that you did not provide sufficiently clear steps that could or would reproduce the performance bug or hang bug you experience. Hang bug and performance bug are not necessarly easy to demonstrate with clear steps. And I'm trying to be fair with you here: I really do not know if there is something worth fixing from the description you have given in this blog.

    Some people have given your description an honest trial to reproduce and could not:



    Can't reproduce what you describe. Seems something depending on your config / situation.



  27. pmbAustin says:

    Don't assume it only happens on HUGE pages.

    A perfect example happened just last night to me.  I simply clicked on a page that had ONE instance of an embedded YouTube video, and clicked play.  Then I tried to click the "expand to full screen", and it went to full screen, and was just blank/black.  Sound continued to play, but no rendering of the image.  Then Escape wouldn't even get me out of full screen mode. I had to alt-tab away to get to task manager, and sure enough, one of the iexplore.exe processes was spinning away at 25 percent!  And the process size was actually under 400K.

    So don't get distracted by HUGE pages that kill any browser.  I'm just trying to get you "easy to force/reproduce" instructions.  It can happen at any time, really, even on smaller pages.

    I don't understand how anyone can't see this.  It happens nearly EVERY DAY to me on MULTIPLE devices and machines.  It's one of the most consistent, constant problems I experience in Windows.  I think other people are just oblivious to it… when they have a weird problem, they probably just close IE or the tab and move on.  Or they never keep multiple tabs open for more than an hour.  I don't know, but this is a MAJOR and EASY TO SEE  problem, so I'm simply not going to believe I'm the only one in the universe that sees this, or that there's anything specific to my hardware or installs (the PCs and devices are VERY different).

    There isn't a deterministic way to reproduce it, which is the other problem.  It happens frequently, but not predictably.  I've found some ways to force it, but even those aren't 100%.  Just look for an iexplore.exe process growing north of 500k (though that's obviously not required, it's usually a hint) and then suddenly taking up 25% of the CPU with tabs not responding.  Wait as long as you want, it won't come back.

  28. Gérard Talbot says:


    > I simply clicked on a page that had ONE instance of an embedded YouTube video, and clicked play. (…)

    Correction. You simply clicked on an *_unidentified_* page with an *_unknown_* URL, etc..

    > was just blank/black.  Sound continued to play, but no rendering of the image.

    I assume you mean video and not image here. That would be another bug report. One issue per bug report.


    Your bug description in this blog and in bug 926585 often lack useful information, worthy information, information that could or would help identify the causes …

    Are you able to reproduce the problem with add-ons disabled? This is important information.

    Are you able to reproduce the problem with pages that have no Flash? This is important information.

    More questions you haven't answered yet:

    Are you using 64-bit or 32-bit IE?

    Do you have "Enable Enhanced Protected Mode" and "Enable 64-bit processes for enhanced protected mode" checkboxes checked?

    Do you have smooth scrolling enabled?

    Have you checked your memory chips? (There is a way to verify that your RAM chips are not faulty or defective).

    Are you using the latest version of IE11 (it is IE11.0.10)?

    Have you tried the 2 pages I mentioned?

    And you should report all these bits of information into a bug report (using formal and factual sentences). Other people already have been asking you some of these questions in this blog.

    > There isn't a deterministic way to reproduce it

    If the problems you experienced are so frequent, then I believe there could (or should) be a way to identify the conditions and then create a reduced testcase.


  29. pmbAustin says:

    This is so easy to experience, I can't imagine how to give you more information.  This should be happening to everyone based on my experiences.

    I don't use any add ons (I'm not even aware IE supports add ons).

    I don't visit pages that have Flash that I'm aware of (unless YouTube is still using flash for embedded videos, and I don't think it is).

    I'm using 64-bit IE.

    I do not have those checkboxes checked on this machine I'm on (Enhanced Protected Mode, 64-bit).  On the ones at home, I just have default installs, and have not fiddled with those settings, so they are whatever they default to.

    Ditto the smooth scrolling option… it's whatever is the default (yes, on this box).

    My memory is not faulty.  There's no way it's been faulty across three laptops, and two desktops, over years, from IE9 to IE11, on both new and old hardware.  This is a CONSISTENT bug.  It ALWAYS happens.  Regardless.

    I've pointed out that changing the "use software rendering" setting alters the symptoms, but the problem still exists.  WIth that setting on, I don't ever seem to get the "white" or "flashing white" tabs/windows.  It just eventually stops rendering (i.e. the page freezes).

    I am always on the latest version of IE (I have automatic updates on, and always update and reboot as soon as updates are available).

    I can't understand why YOU can't reproduce this or haven't seen it.  I feel like you're asking me to describe this "air thing" I speak of, when it's all around you.  From my experience and perspective, it's impossible to NOT experience it in any given week, and lately, it's been any given DAY.

    Stop trying to pretend I'm making this up.  "Air" actually exists, and so does this incredibly annoying bug.

  30. Gérard Talbot says:


    > I don't use any add ons (I'm not even aware IE supports add ons).

    This page…/manage-add-ons

    explains how you can turn off add-ons (run in no add-ons mode) or selectively remove add-ons.

    Flash is an add-on. Visit…/about

    to know if you are using the latest version of it.


    While Microsoft's own add-ons work flawlessly most of the time, third-party add-ons can spell trouble more frequently. It might mean that Internet Explorer does not start, works slowly, stops responding, or some content is not displayed correctly on web pages.


    Internet Explorer 11 Troubleshooting

    > I can't understand why YOU can't reproduce this or haven't seen it. (…)

    > Stop trying to pretend I'm making this up.

    What's important for you is to have bug triagers reproduce the problem you have, not me. And have IE developers understand clearly what is happening and how to reproduce the problem: so best place is not necessarly in this blog but over at connect IE feedback.

    As I already told you, the factual, helpful and formal info should be in a bug report. And I have suggested twice that I do not know if there is something worth fixing from the bug description you gave. The cause and source is not known, not clear so far; it seems your graphic card has limited capability or is not performing well… and on the other hand, you have provided not-so-good examples of webpages causing the problem you see.

    In any case, I do not pretend you're making this up. I do pretend you have not been providing as much helpful information as possible from the beginning. Stating and repeating many times how often, how serious, how annoying a problem is for you is not by itself helpful and does not contribute to make it any easier to reproduce or investigate. Deal with this: try to be helpful and specific where and when it matters.


  31. pmbAustin says:

    Honestly, I feel like YOU are being less than helpful.  Or at least not listening to me.

    The biggest requirement for experiencing this bug is patience.  It ALWAYS happens if you wait long enough.  Leave your browser open with a dozen tabs for days and you WILL experience it.   There's little more data I can add, because there isn't any predictable way I've found to trigger it at will.  It just happens.  When it happens, there's almost always some different sequence of events that led up to it.  It seems to me hitting this bug is INEVITABLE, as long as you have multiple tabs open, and leave IE and the tabs open for a long time.  I can't give you specific sites, because THERE ARE NONE.  I've bent over backwards to try and manufacture some sequence of pages or actions that will trigger the bug faster than others, but all I have is what I've given you.

    When I start to experience page turns that "slow down" over time… or when sound (like the 'ping' when a page displays a modal dialog, or the 'click' of a page-turn) starts to get out of sync with the visuals… that's another clue it's starting to happen.  It means a process is getting large, performance is nose-diving, and soon rending problems will appear, and about that time, the 'large' process will suddenly spike CPU and stay there.  Rarely, it will come back down after a minute or two, but mostly it will just sit there pegging the CPU at 25% like it's in an endless loop.

    All you need to do is monitor your iexplore.exe process sizes, while you're using IE.  Open a dozen pages.  And browse normally.  It might take a day or two.  Just don't close the browser.  Keep opening new tabs every once in a while.  Let others just sit.  Don't close tabs.

    It'll happen. Trust me.  If you have any patience at all, you WILL see it.  I've never been able to NOT see it.

    I've given you all the info I have.  I've given it a dozen times on this forum over the years.  There are always people who say "Yeah, me too!", so it's definitely not just me.  It happens on ANY system I use.  It's just that if you constantly close IE, or only use one tab, you'll probably never hit it.  Or if you just assume IE is slow and sluggish from time to time, you might just dismiss it and not realize you're hitting it.  If you shut down your laptop every day, you probably "clear things out" before you get there.  I don't know.  I just know what I experience on a too-regular basis.

    It happened again last night.  Came home from a movie, picked up the laptop and started browsing, and after 30 minutes or so, the pages were turning REALLY slowly, and the audio "clicks" were lagging the page turn by a full second or so.  Sure enough, one of the processes was up to 800,000k.  There was no reason for it.  No "large" pages loaded.  Killing the process, and performance was restored, and no process was over 100,000k.

  32. pmbAustin says:

    Happened again just now. Yoga2Pro laptop (next to top of the line).  Just open the page.  Browsed the home page, and clicked on a link… instead of seeing the new page, the tab just went white.  Sure enough, checked Task Manager, and there was an iexplore.exe process taking 600,000k+, and chewing up a steady 20%+ of the CPU.  Killed it, the page reloaded and everything was fine.

    Happens pretty much DAILY these days.

  33. Simon says:

    This happens a lot too on my device (Surface Pro 1)

Comments are closed.

Skip to main content