New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 806527 link

Starred by 6 users
Status: WontFix
Owner:
kozy@chromium.org
Closed: Sep 25
Cc:
█ abdulsyed@chromium.org
gov...@chromium.org
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Console is cleared after refresh, messages are shown for a split second

Reported by tvanderl...@gmail.com, Jan 27 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
1. Open attached console-refresh-bug.html
2. Open DevTools
3. Observe that "should show up" is shown in the console
4. Refresh the page (ctrl + R or click the refresh button)
5. Observe that the console is completely empty
6. Hide the Devtools
7. Open the Devtools
8. Observe that the message is again there.

What is the expected behavior?
Console is not cleared after a refresh (the message is there for a very short time and then disappears)

What went wrong?
The console is empty after a refresh, making debugging a lot harder. Now I have to re-open devtools after a refresh to get the correct console.

Did this work before? Yes 63

Chrome version: 64.0.3282.119  Channel: stable
OS Version: 16.04
Flash Version: 

Started breaking after upgrading to Chrome 64. Was working just fine before. I think it has something to do with the grouping of messages.
console-refresh-bug.html
103 bytes View Download

Comment 1 by tvanderl...@gmail.com, Jan 27 2018 

This is probably an issue with the Vimium extension, as I found https://github.com/philc/vimium/issues/2907 Disabling Vimium resolves the issue. Still makes me wonder what changed in Chrome 63 and 64 that makes this extension break.

Comment 2 by krajshree@chromium.org, Jan 28 2018

Labels: Needs-Bisect Needs-Triage-M64

Comment 3 by sc00335...@techmahindra.com, Jan 29 2018

Cc: sc00335...@techmahindra.com
Components: Platform>Extensions
Labels: -Pri-2 -Needs-Bisect Triaged-ET RegressedIn-64 M-64 FoundIn-65 FoundIn-64 FoundIn-66 Target-66 Target-65 Target-64 hasbisect OS-Mac OS-Windows Pri-1
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on reported version 64.0.3282.119 and on latest canary 66.0.3334.0 using Ubuntu 14.04,Mac 10.13.1 and Windows 10 after adding vimium extension.

Good Build: 64.0.3282.67
Bad Build: 64.0.3282.71

Unable to perform per-revision bisect as this issue is broken in branch builds.Hence assigning from manual changelog

CR: https://chromium.googlesource.com/chromium/src/+log/64.0.3282.67..64.0.3282.71?pretty=fuller&n=10000

Suspecting https://chromium-review.googlesource.com/841145 from changelog.

@dgozman: Please confirm the bug and help in re-assigning if it is not related to your change.

Adding RB-Stable for M-64, Please change if not the case.

Thanks!

Comment 4 by sc00335...@techmahindra.com, Jan 29 2018

Labels: ReleaseBlock-Stable

Comment 5 by manoranj...@chromium.org, Jan 30 2018

Cc: gov...@chromium.org abdulsyed@chromium.org
We can punt this issue to M-65.

Comment 6 by abdulsyed@chromium.org, Jan 31 2018

Labels: -M-64 M-65

Comment 7 by dgozman@chromium.org, Feb 5 2018

Labels: -ReleaseBlock-Stable
Owner: kozy@chromium.org
Not a blocker. Over to kozy@ to double check why something has changed at all.

Comment 8 by tvanderl...@gmail.com, Feb 16 2018 

Per https://github.com/philc/vimium/issues/2907#issuecomment-366205655 this issue appears to be fixed in Vimium (for now). The corresponding fix was https://github.com/philc/vimium/pull/2939 which disabled an optimization of Vimium. It might be still worthwhile to investigate why this optimization broke the Dev Tools in Chrome 64, but for now Vimium is working again.

Comment 9 by kozy@chromium.org, Sep 25

Status: WontFix (was: Assigned)
►

Sign in to add a comment