Edge perf is terrible with Spell Check on GitHub issues

Confirmed Issue #10985002 • Assigned to Lee H.

Details

Author
Oren N.
Created
Feb 16, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

If you enter a reasonable sized stack trace in a GitHub issue, the textbox becomes barely usable to enter in text around the issue description.

The issue appears to be that Edge is struggling with all of the spelling errors in a typical stack trace.

Turning of spell checking isn’t the answer because the rest of the text in the issue should be spell checked. Chrome doesn’t suffer this perf issue either for the same amount of spelling errors in the textbox.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rico M.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Rico M.” to “Lee H.”

    • Thank you for letting us know about this issue.  We would like to investigate further. Would you be able to provide addtional information? 

       

      Either:

      1. include the Windows build number, URL, textbox and ‘reasonable sized stack trace’ for a concrete repro
      • or, better yet, -

      2.  Grab a Edge etl: (** NOTE: this may grab memory [e.g. stacks] from your system, so please don’t include any sensitive data **)
      (a) From an admin command prompt:
      (i) cd %windir%\system32
      (ii) wpr -start EdgeBrowser
      (iii) ++ Exercise repro ++
      (iv) wpr -stop c:\foo.etl 10985002
      (v) Attach c:\foo.etl to bug

       

      Thanks!

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

    Sign in