Issue metadata
Sign in to add a comment
|
Speed: Forced tab re-focus on inspector launch after significant delay.
Reported by
tomead...@gmail.com,
Sep 22
|
||||||||||||||||||||||||
Issue descriptionForced tab re-focus on inspector launch after significant delay. To re-produce: 1. Open multiple tabs. 2. Launch DevTools (using right-click 'inspect'). 3. Navigate to other tab (before DevTools opens). Expected: - DevTools should open immediately. - Tab should not force re-focus when DevTools becomes available. Actual: - DevTools opens extremely slow compared to last build (10-15 seconds). - During this period a user may want to navigate to other tabs. When DevTools eventually launches and is ready for use the tab re-focuses and disrupts other navigation/web app use. Test: - Tested with activity monitor for any memory usage spikes, nothing unordinary. Regression, last working version: - Major version 68 Important system specs: - MACOS HIGH SIERRA 10.13.6 - 2.2Ghz intel i7 Processor - 1.5GB Intel Iris GPU - 16GB DDR3 RAM - SSD Storage
,
Sep 23
,
Sep 25
Able to reproduce the issue on reported chrome version 69.0.3497.100 also on latest chrome 71.0.3559.0 using Mac 10.13.6 and Windows 10. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. NOTE: Observed the Forced re-focus when DevTools becomes available but not seen slowness and issue not seen on Ubuntu. Thanks!
,
Oct 4
> Same behavior is seen on M60(60.0.3112.113) Which same behavior was seen on M60? The tab re-focus or the slow opening of devtools? The slow opening of devtools seems like the real problem. It shouldn't take 10-15 seconds to launch it. On my machines (workstation, laptop, etc., all Windows) it takes more like one second to launch. Some questions: 1) Does this happen on all pages? Specifically, does this happen on about:blank? If it only happens on some pages then what are they? 2) If this happens on all pages then can you please record a trace of this happening? chrome://tracing or (my personal preference) an ETW trace (https://tinyurl.com/uiforetw). If you get such a trace covering the time from when you request devtools to when it opens then I can take a look and try to figure out what is going on. It might be helpful to, say, tap the 'ctrl' key when devtools opens as an indicator. That is, start tracing, select Inspect from the menu, then wait for devtools to open (don't change tabs or do anything else), then type 'ctrl' as soon as devtools opens, then save the trace (Ctrl+Win+R).
,
Oct 15
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tomead...@gmail.com
, Sep 22