Issue metadata
Sign in to add a comment
|
input type password causing CPU leak when other form controls are being generated by innerHTML on the same page
Reported by
ea...@alphasoftware.com,
Nov 16 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. run the attached simple HTML page 2. the peak CPU usage continues to rise 3. after a few minutes chrome will lock up 4. change the input type from password to text in the file and refresh 5. CPU leak apparently gone What is the expected behavior? What went wrong? when a input type password element is on the same page with content being set through innerHTML, in which there is a form control (input/button), the CPU usage leaks. Did this work before? No Chrome version: 62.0.3202.94 Channel: stable OS Version: 10.0 Flash Version:
,
Nov 30 2017
The NextAction date has arrived: 2017-11-30
,
Dec 13 2017
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Nov 16 2017NextAction: 2017-11-30