Issue metadata
Sign in to add a comment
|
No error codes (description) in Developer Console
Reported by
ilya.dis...@gmail.com,
Apr 23 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. Open Developer Console on page with errors. 2. Update this page in Developer Console. 3. Now we see " 0 () " instead error codes. What is the expected behavior? What went wrong? Errors parsing failure. Did this work before? Yes M65? Chrome version: 66.0.3359.117 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 24 2018
ilya.displax@ Thanks for the issue. Tested this issue on Windows 10 on the reported version 66.0.3359.117 and the latest Canary 68.0.3403.0 by following the below steps. 1. launched Chrome and navigated to www.google.ru 2. Couldn't see any errors on Devtools -> Console. 3. On opening a new tab, on NTP, can find errors on Devtools -> Console, but couldn't find any 0 (). Attached is the screen shot for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also Request you to provide a URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Apr 24 2018
This happens with all errors type "net::ERR_*" , no matter which ones and which site. Maybe it happens with other error types too. For example, simple test on https://www.ssllabs.com/ssltest/viewMyClient.html 1. Open this URL and wait when test finished. 2. Open the console and see correct errors. Everything is as it should be. 3. Refresh this page via Ctrl + F5 from Developer Console. Instead of correct errors it show 0 () in the same places and situations. I attached video for a better understanding of the situation. Tested this on Win 7 with Chrome 65 - works correct. Tested this on Win 7 with Chrome 66 - same issue.
,
Apr 24 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 25 2018
ilya.displax@ Thanks for the update. Able to reproduce this issue on Windows 10, Mac OS 10.12.6 and Ubuntu 14.04 on the latest Canary 68.0.3406.0 and reported version 66.0.3359.117 as per comment #3. Bisect Information: =================== Good Build: 66.0.3348.0 (Revision - 536934) Bad Build : 66.0.3349.0 (Revision - 537110) On executing the per-revision bisect script, below is the Changelog URL: https://chromium.googlesource.com/chromium/src/+log/5844f7146bca1e7c91e8f03de044ab408850d611..848d697da0766cc108c5f869f38128b8ff52df94 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/920541 pfeldman@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Adding ReleaseBlock-Stable as this is a recent recent regression. Please feel free to remove if it is not applicable. Thanks.
,
Apr 25 2018
,
May 2 2018
*** Bulk Edit *** M67 Stable promotion is coming soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. If fix is already merged to M67 and nothing else is pending, pls mark the bug as fixed. Thank you.
,
May 2 2018
,
May 2 2018
Not a stable blocker, but we would need to fix it in M68.
,
Jun 27 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Apr 24 2018