Issue metadata
Sign in to add a comment
|
JavaScript Click Performance Issue
Reported by
cbeedham@googlemail.com,
Feb 7 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: 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:
,
Feb 8 2018
@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!
,
Feb 16 2018
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
,
Feb 16 2018
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
,
Feb 16 2018
,
Feb 19 2018
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!
,
Feb 22 2018
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.
,
Feb 26 2018
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 |
|||||||||||||||||||||||
Comment 1 by susanjun...@techmahindra.com
, Feb 7 2018