focus function taking unusual amount of time to complete in 62
Reported by
vishal.k...@gmail.com,
Nov 20 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Execute a mouseup resulting in a focus on an element 2. Wait for focus completion (takes a few seconds to complete) What is the expected behavior? 1. Execute a mouseup resulting in a focus on an element 2. Wait for focus completion (should complete in tens of milliseconds) What went wrong? Focus function is taking several seconds to complete. The performance call tree is attached to the ticket. This is not a problem in the dev and canary releases which are version 64. It seems to be present in the 63 beta channel. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: 62.0.3202.94 Flash Version:
,
Nov 20 2017
Forgot to mention that this issue was not present in 61. Also, it is reproducible in Windows OS.
,
Nov 20 2017
,
Nov 20 2017
,
Nov 21 2017
Unable to reproduce the issue on reported version 62.0.3202.94, latest build 64.0.3273.3 and beta 63.0.3239.52 using ubuntu 14.04 and Win 10 by following below steps 1. Navigate to https://www.isc.ca/ISCForms/Pages/default.aspx 2. Press F12 to open Dev tools, go to performance tab and record while hovering the page using mouse 3. Observe total time in call Tree, completes in approx 20-40 ms @ vishal: Could you retry the scenario by create a new profile or removing unwanted extensions and provide your observation. Also provide sample URL that would help us in triaging the issue from TE-end
,
Nov 21 2017
Looks like a duplicate of issue 781026 broken in 62 and fixed in 63 (Stable in 14 days on Dec 5)
,
Nov 21 2017
It might be a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=781026. I don't see any performance lag in 63.0.3239.59 Thanks
,
Nov 21 2017
Thank you for providing more feedback. Adding requester "divya.padigela@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
,
Nov 22 2017
@Vishal: Could you please let us know if the issue still persists on clean profile as per C#5 using latest stable version Stable is moving to M-63 tentatively in 2-3 weeks, could you please retry the scenario when stable is available on M-63 as the issue is not reproduce from TE-end
,
Nov 22 2017
@Priya: The issue persists even with a new profile on the current stable version. I will retry after 63 stable release and will update if that issue is rectified in the stable version. Thanks
,
Nov 22 2017
Thank you for providing more feedback. Adding requester "divya.padigela@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
,
Nov 24 2017
As per comment#10 waiting for reporter to respond. Hence adding Needs-Feedback label @Reporter: Could you check the behaviour in latest beta. You can download beta builds from https://www.chromium.org/getting-involved/dev-channel
,
Nov 24 2017
I have tried the latest beta build mentioned below and have not been able to replicate this issue. Everything looks good. Thanks! Version 63.0.3239.59 (Official Build) beta (64-bit)
,
Nov 24 2017
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
,
Nov 27 2017
Thanks for the update, closing the issue as per above comment.! |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by vishal.k...@gmail.com
, Nov 20 201758.3 KB
58.3 KB View Download