Issue metadata
Sign in to add a comment
|
DevTools shows negative time in scripting
Reported by
n...@ioncube.com,
Aug 10
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: What I am doing is: 1. Use ioncube24.com to display monitor results 2. Start performance profiling 3. Changing the time range shown for results, triggering chart redrawing and XHR requests. What is the expected behavior? I should see the amount of time spent in scripting as a positive number (and used to when last doing so a few weeks ago). What went wrong? I see a negative time spent in scripting, a solid yellow region, a mangled doughnut chart, despite a large idle time. Did this work before? Yes Uncertain, but probably wherever the current release was a month or two ago. Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version:
,
Aug 12
,
Aug 13
,
Aug 13
,
Aug 13
Unable to reproduce the issue on reported chrome version 68.0.3440.106 using Windows 10. Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome 2. Navigated the URL " ioncube24.com " 3. Opened Dev tools >> Performance Tab>>Started performance profiling and stopped As we are seen that scripting has a positive number @Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end. Thanks.!
,
Aug 13
It happens on a specific view once logged in. I'll setup a test account, let some data accumulate if necessary and email login credentials.
,
Aug 13
Just emailed login details. Testing different versions using Browserstack, the issue appeared in version 65.
,
Aug 17
Full details per request: To reproduce: 1) login with crtest / crtest873106 2) after interface loads, click on the chart (ignore any request to update profile) 3) On the monitors view, click F12 and start a performance recording 4) Wait a few seconds then on the chart change time range from 12 hours to 6 hours. 5) Stop recording The negative script time should then be evident. I tested various versions of Chrome on W10 over browserstack and the issue seems to have appeared in 65 onwards. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by n...@ioncube.com
, Aug 1021.9 KB
21.9 KB View Download