Link to JSBin demo: http://output.jsbin.com/zatehidado

dan@ Thank you for the issue.

unable to reproduce the issue on Windows 10, MacOS 10.12.6 using  Stable 60.0.3112.78 and canary 62.0.3172.0 with the below steps

1.Opened the given url
2. Enabled the spellcheck and entered some input.
3.Not observed any lag while entering text. 

Please find the attached screen cast and confirm if anything missed here.
Request you please try the issue on new profile without any extensions/flags and update the thread if the issue still exists.

Thanks

Deleted: spellcheck.mp4 2.3 MB

	spellcheck.mp4 2.3 MB View Download

Hi Susan,

Thank you for taking the time to look into it. I have created a new profile and I can still reproduce this issue. Please note that the effect becomes much more apparent after you're several lines into the text. Attached screencast.

Deleted: typing-lag.mov 16.2 MB

typing-lag.mov 16.2 MB Download

Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Are you able to provide a chrome trace? See chrome://tracing and https://www.chromium.org/developers/how-tos/trace-event-profiling-tool

A javascript & rendering trace may be helpful; or select Edit Categories and Select All.

I am attaching the trace file for the laggy behavior.

Deleted: lag_trace.json.gz 2.2 MB

lag_trace.json.gz 2.2 MB Download

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looking from the trace the GPU the bulk of the latency in the input events. 150-160ms to swap

ccameron@ are you aware of any GPU issues in Chrome 60 on mac?

It seems that I cannot reproduce as constantly as initially. What I've observed, and it may be a stupid observation, but it may lead to some clues — if the battery drops under about 10% the lag seems to disappear; is there any low battery optimization in Chrome that may be impacting the spell checking? Or is it something at the OS level?

-> ccameron@ for thoughts, answer to c#9

Re #10, I would generally think this to be the opposite. If the battery is low, CoreAnimation starts throttling to a lower framerate.

What happens if you kill the GPU process or restart Chrome? Does the issue come back?

Could you attach the output of going to about:gpu as a PDF to this bug.

We can try to reproduce this bug on the same GPU as you have, but this is likely to be system specific.

As of now, I can only reproduce the problem very infrequently. However, when it happens, the effect seems to linger until I restart Chrome (refreshing the page does not help). I am attaching nonetheless the about:gpu summary. 

Deleted: chrome---gpu.pdf 319 KB

chrome---gpu.pdf 319 KB Download

Thank you for providing more feedback. Adding requester "ccameron@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The NextAction date has arrived: 2017-08-15

[mac bug triage] ccameron@ - ping.

This doesn't seem like an old GPU, so I'm out of ideas on this one.

Could this be like some type of leak of handles or something? (as restarting helps, would it be useful to get the user to dump the proc info when it is happening?)

[Mac triage] Marking available to take it out of our queue.

I can confirm that this behavior is occurring consistently on a 2016 MacBook Pro 13" with a Intel Iris Graphics 540 1536 MB graphics card.  It happens in Chrome 63.0.3239.108 as well as in Canary 65.0.3299.0.

I've attached an example HTML document which demonstrates this behavior. Clicking on any of the paragraphs with misspelled (latin) words causes major slowdown.  Note that in practice, where there are event handlers attached to the elements in the contenteditable area, this slowdown is even more apparent and makes writing near impossible.

Disabling Chrome's hardware acceleration stops the issue from happening and the behavior is as expected.

I've also attached about:gpu as well as a profile run when the behavior occurs.

Deleted: chrome.html 3.5 KB

chrome.html 3.5 KB View Download

Deleted: about-gpu.htm 62.3 KB

about-gpu.htm 62.3 KB View Download

Deleted: Screen Shot 2017-12-20 at 7.02.45 PM.png 545 KB

	Screen Shot 2017-12-20 at 7.02.45 PM.png 545 KB View Download

Deleted: Profile-20171220T190318 16.1 MB

Profile-20171220T190318 16.1 MB Download