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

Issue 809994 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

JavaScript Click Performance Issue

Reported by cbeedham@googlemail.com, Feb 7 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36

Steps to reproduce the problem:
1. Create an amazing web product
2. Click events work perfectly fine in chrome 63
3. Upgrade to 64
4. Do the same events again and experience the lag

What is the expected behavior?
Not to be slow

What went wrong?
click events have become a lot slower since upgrading

Did this work before? Yes 63

Chrome version: 64.0.3282.140  Channel: stable
OS Version: 10.0
Flash Version:
 
2018-02-07 14_58_15-Photos.png
11.2 KB View Download
Labels: Needs-Bisect Needs-Triage-M64
Labels: Triaged-ET Needs-Feedback
@Reporter: Could you please provide sample URL or test case with click events to test this issue. This would help in further triaging of the issue.

Thanks!
Unfortunately I cannot provide details for the system but I have noticed that the issue is not happening in FireFox and we are currently asking our client base to downgrade to version 63 or move to vivaldi. 

On one of our products we have a JQuery Dialog with a bootstrap tab inside, simply clicking these tabs will eventually cause a lag for a few seconds. 

I have attached the chrome performance export
Profile-20180216T090601.json
12.5 MB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 16 2018

Cc: sc00335...@techmahindra.com
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by bokan@chromium.org, Feb 16 2018

Components: -Blink Blink>Input
Cc: -sc00335...@techmahindra.com sindhu.chelamcherla@chromium.org
Labels: TE-NeedsTriageHelp
It will not be possible to test this issue from TE end without any sample file/URL(as per comment#4). Hence adding TE-NeedsTriageHelp label and requesting someone from Blink>Input team to please have a look at the performance log attached.

Thanks!
Components: -Blink>Input Blink>JavaScript
This isn't an input issue but perhaps a JS performance problem. However nothing from the trace seems to point to that. If we don't have a reproduction URI it is really hard for us to advise.

The trace indicates that javascript was being executed here:

{frame: "0x3947780421f0",
 functionName: "mouseup",
 scriptId: "2231",
 url: "http://localhost/Scripting/bundles/core?v=BEoPJUnzjsJnDcMNm1cnQDy82tQHkPRySKASzZbjNLc1",
 lineNumber: 1,
 columnNumber: 104908}

This function took 1,861.719 ms of CPU time. So it is really poorly behaving JS function.
Status: WontFix (was: Unconfirmed)
Indeed. There are also nested mouse move events at the same time. To re-iterate: Without an example URL or workload this is not actionable.

Please reopen if you can provide this.

Sign in to add a comment