Issue metadata
Sign in to add a comment
|
Console always preserves log
Reported by
m.go...@gmail.com,
Jan 25 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: I don't know how to reproduce it as it doesn't happen on a fresh profile. It does, however, happen with all the extensions disabled. This seems to indicate a specific configuration might be causing an issue. What is the expected behavior? What went wrong? The console logs are always preserved, regardless of whether the "Preserve log" checkbox is checked or not. Did this work before? Yes It worked fine 2-3 weeks ago. Chrome version: 66.0.3331.0 Channel: canary OS Version: OS X 10.13.3 Flash Version: Can I submit my Canary config to you somehow so that you can reproduce it? Or produce any diagnostic log?
,
Jan 26 2018
Interesting; it seems it doesn't happen on all pages. It does happen on a Webpack dev server of the app I'm currently developing, running on https://localhost:8084 with an invalid self-signed cert that I'm telling the browser to accept. The site is not public yet so I can't show the whole page but I've recorded a DevTools pane. I'm refreshing the page once in the screencast and you can see that the Google Tag Manager error & 3 warnings happen twice. When I refresh the page yet another time, a third set of messages appears etc. (I had to cut out the second refresh as the video file got too big).
,
Jan 26 2018
Could it be perhaps caused by the WebSocket connection the Webpack Dev Server maintains with the browser? This still doesn't happen on a fresh profile, though, only on my current one. Restarting the browser, re-opening the page & DevTools etc. doesn't help, though. Manually calling `clear()` in the console does clear it, the same when I click on the "Clear console" button.
,
Jan 29 2018
,
Jan 29 2018
Thanks for filing the issue!! Unable to reproduce this issue on reported version 66.0.3331.0 canary using Mac 10.13.1 with sample HTML file we have. 1. Started simple HTTP server using python -m SimpleHTTPServer 8084 2. In browser navigated to http://localhost:8084/test.html and opened devtools and reloaded page when preserve log is disabled. Attaching screencast for reference. @Reporter: Please check the video and let us know if we miss anything. Also please provide sample test file to test this issue. This would help in further triaging. Thanks!
,
Jan 31 2018
Thanks for the report. Usually upon refresh with 'Preserve log' enabled, DevTools will detect any navigations and add a console message saying "Navigated to ______", but I don't see this message in your screencast in comment #2. - If you enable 'Preserve log', do you see the "Navigated to ______" messages when you refresh? If not, perhaps refreshing isn't actually refreshing. - Does refreshing clear requests in the Network Panel when Network's 'Preserve log' is off? If it does not, the issue may be larger than just console. - Could you check DevTools on DevTools to see if there are errors? ( http://stackoverflow.com/a/12291163/89484 )
,
Jan 31 2018
,
Feb 15 2018
Without being able to reproduce this, there isn't much we can do. Marking as Archived for now. If you have more info, please feel free to comment. A fix landed in a recent Canary (66.0.3345.0) that addressed https://crbug.com/809970 It's not the same symptom, but perhaps you could update Canary and see if it helped? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by einbinder@chromium.org
, Jan 25 2018