GitHub slowness

Fixed Issue #11594880


- O.
Apr 11, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

While using GitHub, Edge sometimes slows down (especially when I delete some text with always pressed backspace button during file editing).


0 attachments

    Comments and activity

    • And sometimes if I want to select a specific line during file edit, Edge select instead the first line of file.

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Lee H.”

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

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Assigned To to “John-David D.”

      Changed Status to “Confirmed”

    • Try also with touch input.

    • Hi Orazio!

      Can you point me to a sample file to edit to repro the issue. When I try using Edge 15.16.184 I can’t repro the slow down when editing a file and pressing backspace (to delete content).

    • Try this with touch input:

      Sometimes when I tried to edit it, Edge tab appeared grey (freezed) for some seconds. Try also with keeping backspace (of virtual keyboard) pressed for many time, and you will see that after releasing it the deleting still continue (like a delay).

      Thanks! I can reproduce the issue. 

    • Same thing happen with Disqus in presence of much many comments.

    • Microsoft Edge Team

      Changed Assigned To from “John-David D.” to “Lee H.”

      Changed Assigned To from “Lee H.” to “Todd R.”

      Changed Status from “Confirmed” to “Fixed”

      I’ve tested this issue on internal build 16241 / Edge 41.16241.0.0, and it appears to be resolved: typing performance in the indicated scenarios is indistinguishable from Chrome, and the grey/frozen tab behavior is no longer present.

      There has been heavy investment in addressing perf-related issues on our team over this last iteration, and I suspect the root cause of this bug has been addressed.

      If you you still see this on an Insider Build, can you please let me know the Windows build number, so I can try to reproduce in a closer environment?  Additionally, would you be willing to capture some perf traces?  That would give us what we need.

      Instructions for doing that can be found here:

      Thanks for the bug report, and please let us know if you run into any other issues.

    • Thanks. If I get this bug again, i will follow this tutorial. ;)

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

    Sign in