New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 616205 link

Starred by 1 user
Status: Assigned
Owner:
lazyboy@chromium.org
Cc:
█ adhintz@google.com
rbyers@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

PasswordAlert regex takes 90ms on amazon.com on a Macbook Pro

Project Member Reported by esprehn@chromium.org, May 31 2016 
Google Chrome	53.0.2748.0 (Official Build) canary (64-bit)
Revision	20447ead8ba4b9bf3310da0d80a23a199aba1d60-refs/heads/master@{#395748}
OS	Mac OS X 
Blink	537.36 (@20447ead8ba4b9bf3310da0d80a23a199aba1d60)

This is on my Retina MBP.

What steps will reproduce the problem?
(1) Open the devtools timeline and click record.
(2) Load http://www.amazon.com/Bostonian-Purnel-Mens-Oxford/dp/B008PPWAS2/ref=pd_sim_309_3?ie=UTF8&refRID=0JGE1N91TG7VWFTPN2CH&dpID=31-8qEGFE5L&dpSrc=sims&preST=_AC_UL160_SR160%2C160_

Comment 1 by esprehn@chromium.org, May 31 2016 

Here's the trace.
TimelineRawData-20160531T132654.json.zip
915 KB Download
slow-regex.png
68.4 KB View Download
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 1 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 3 by adhintz@google.com, Jun 1 2017 

From my testing on a desktop, for the main Parse HTML (/Boston...) its Evaluate Script of  content_script_compiled.js:1 has a Total Time 25.86 ms

There are several other (4?) Parse HTML (about:blank) that each take between 6ms and 10ms.

The source code is here in case you see any obvious performance things that we could improve: https://github.com/google/password-alert

Comment 4 by rdevlin....@chromium.org, Jun 2 2017

Status: Available (was: Untriaged)
This should be helped some by native extension bindings ( issue 653596 ), which will speed up  the work chrome is doing, but it'll largely boil down to watchword doing a lot.  My guess is that to truly improve this, we'd have to do a few deep dives into what it's doing and how to optimize it.  For that, I think someone on the blink team would be most qualified.
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 4 2018

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Comment 6 by lazyboy@chromium.org, Jun 29 2018

Owner: lazyboy@chromium.org
Status: Assigned (was: Untriaged)
I'll try to repro this myself and will report back.
►

Sign in to add a comment