High CPU usage after having a page open in Private mode for a day or longer

Confirmed Issue #11451669 • Assigned to Kevin H.

Details

Author
Martin C.
Created
Mar 30, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
15.15063
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Open a page in Edge (non-private).
  2. Open a page in Private mode in Edge (for example, Facebook).
  3. Open Task Manager and check Edge’s CPU usage. It should be normal.
  4. Keep the page open in the background for a significant amount of time (for example, a day).
  5. Check Edge’s CPU usage again. Notice that the Edge’s CPU usage is quite high (attaching 100%).
  6. Close the page opened in the Private mode.
  7. Check Edge’s CPU usage once more. The Edge’s CPU usage is back to normal again.

The Edge’s CPU usage should not raise in time.

Attachments

0 attachments

    Comments and activity

    • Changed Title from “High CPU usage after having a page is open in Private mode for a day or longer” to “High CPU usage after having a page open in Private mode for a day or longer”

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Martin,

      Just wanted to let you know that I have started the repro testing.

      Also, did you by chance notice the memory usage?  Tried to repro in the latest insider update?

      The MS Edge Team

    • Hi Steven,

      I do not have a private mode page opened just now.
      I have noticed the CPU usage increase. If a memory usage has increased as well I don’t think it was as significant as the CPU usage.
      No, I haven’t tried to repro on the latest Redstone 3 build.

    • Martin,

      Thanks for the update.

      I still have my testing running.  The latest non-public developer release testing did not have any noticeable memory or CPU increases yet.  It has been about 18 hours.  I did notice the latest insider build was using almost double the memory and had higher CPU as compared to the developer build.

      I will let the test run for at least 48 hours.  If I don’t see issues in the latest developer R3 build, I plan to close this as 'fixed’.  Let me know if you disagree and thanks again for the submission.

      The MS Edge Team

    • Hi Steven,

      I’ll try to repro in the Insider build.

      The issue night be caused by something else - like a closed tab in Private mode, or might require some navigating in Private mode, stepping across a specific API caused by pages… I had not dig it intensively.

      I am sure that the issue is somehow related with Private mode as closing the last Private tab restores the CPU usage back to normal followed by the CPU fan sound and OS responsiveness. It never occurs while only non-private tabs are open.

    • I was able to repro it in an hour or two on 15063.138.

      I have uploaded some dumps for you. Grab them at https://1drv.ms/f/s!Aqp3K4ONaozK2_J_f4wgn6gi8LaO6w (I’m getting server errors while trying to upload their zipped versions here).

    • I am unable to upgrade to 16170 due to Windows 10 Insider Preview 16170 (rs_prerelease) - Error 0x80091007.

    • Hi Martin,

      I think the issue with the uploads is there is a 250 MB limit.

      The information you are providing is helpful.  Appreciate the extra effort you are taking to send the detailed information.

    • Zipped versions had around 100MB. I got server errors even while uploading one-by-one.

    • Microsoft Edge Team

      Changed Assigned To to “Lee H.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Lee H.” to “Steven K.”

      Changed Assigned To from “Steven K.” to “Lee H.”

    • Still happening (Microsoft Edge 40.15063.0.0). In my case, not necessarily after a long amount of time. In less than half an hour the CPU usage raises to 90%+ and goes down after closing the inPrivate window.

    • Microsoft Edge Team

      Changed Assigned To from “Lee H.” to “Kevin H.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in