Unable to reproduce this issue on reported version 67.0.3396.87 using Windows 10 with steps mentioned in comment#0.

On opening New tab page after installing dark theme doesn't show any white flash. Attaching screencast for reference.

@REporter: Please check the screencast and let us know if we miss anything. Any further information on reproducing the issue would help in further triaging of the issue.

Thanks!

Deleted: 853986.mp4 2.6 MB

	853986.mp4 2.6 MB View Download

I can't reproduce it every single time, as my attached video shows, but it happens fairly frequently. I apologize for the large black box across most of the screen, I was hiding parts of the page that I didn't want seen. It does occur in incognito mode as well, but since it can be sporadic I haven't been able to record it there yet. Still trying though.

This clip is really helpful as well because you can see reddit loading last, that time the flash lasted quite a while.

Deleted: 2018-06-20 16-58-47.mkv 6.9 MB

2018-06-20 16-58-47.mkv 6.9 MB Download

It now happens reliably every single time a new incognito window is opened, see attached.

Deleted: 2018-06-20 17-05-29.mp4 5.6 MB

	2018-06-20 17-05-29.mp4 5.6 MB View Download

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

Last one, this is in incognito mode. I bookmarked a few random mods from the Stardew Valley Nexus Mods site and opened the folder at once by middle-clicking. Several of the tabs show the white flash, and it happens almost every time with those pages. The pages in question are:

https://www.nexusmods.com/stardewvalley/mods/189?tab=files
https://www.nexusmods.com/stardewvalley/mods/1809?tab=description

Deleted: 2018-06-20 17-13-01.mp4 3.3 MB

	2018-06-20 17-13-01.mp4 3.3 MB View Download

Able to reproduce the issue on reported version 67.0.3396.87 and latest canary 69.0.3466.0 with steps mentioned in comment#6 using Windows 10, Ubuntu 14.04 and Mac 10.13.3.

This issue is seen from M-60. Considering this issue as Non-Regression and marking as Untriaged.

Thanks!

This was fixed in the compositor, right? I'm guessing the incognito issue is because we can't share data cross tabs.

As of today, this bug is still alive and active in Win 10 builds.

X64 Build - Release, Beta, Dev, Canary.
W32 Build - Dev

The release build was my daily use browser.  I tried various themes and in incognito mode.

All browsers showed the same behavior of a brief flash before showing the rendered page when switching to the background loaded tab from prior tab.

The flash appears to only occur the first time of switch to the background loaded tab.

Hardware Acceleration enabled/disabled does not prevent the problem.

Faster hardware results in more brief of flash.  Disabling acceleration causes slightly longer flash.

Two distinct platforms used.  One Intel laptop with Intel graphics.  One AMD desktop with Nvidia 1070.

I have poked at most every possible option, theme, driver, and tweak I have found or can think of.  The problem persists.

chrishtr: were you previously owning getting this bug fixed? If no, can you find a person who can continue owning this problem?

The Version 69.0.3497.81 (Official Build) (64-bit) update under Windows 10 seems to have possibly made the flash slightly longer.  Might be my imagination.  Either way, it is blinding, annoying, and persists. :(

As I am simply a user, I am limited to what I can do to prevent blinding flashes every tab change.  Here is what I have toyed with today:

Playing with the following did not fix it:

chrome://flags/#overlay-strategies
chrome://flags/#disable-accelerated-2d-canvas
chrome://flags/#disable-accelerated-video-decode
chrome://flags/#lcd-text-aa
chrome://flags/#gpu-rasterization-msaa-sample-count
chrome://flags/#enable-viz-display-compositor
chrome://flags/#ignore-gpu-blacklist
chrome://flags/#disable-software-rasterizer
chrome://flags/#enable-gpu-rasterization
chrome://flags/#enable-oop-rasterization
chrome://flags/#enable-zero-copy
chrome://flags/#enable-gpu-appcontainer

I threw caution into the wind and messed with:

chrome://flags/#ignore-gpu-blacklist
chrome://flags/#enable-fast-unload
chrome://flags/#enable-history-entry-requires-user-gesture
chrome://flags/#smooth-scrolling
chrome://flags/#overlay-scrollbars
chrome://flags/#overlay-scrollbars-flash-when-mouse-enter
chrome://flags/#save-page-as-mhtml
chrome://flags/#enable-quic
chrome://flags/#enable-javascript-harmony
chrome://flags/#enable-future-v8-vm-features
chrome://flags/#enable-gpu-rasterization
chrome://flags/#gpu-rasterization-msaa-sample-count
chrome://flags/#enable-experimental-web-platform-features
chrome://flags/#enable-devtools-experiments
chrome://flags/#enable-scroll-prediction
chrome://flags/#top-chrome-md
chrome://flags/#enable-hdr
chrome://flags/#pull-to-refresh
chrome://flags/#num-raster-threads
chrome://flags/#enable-message-center-new-style-notification
chrome://flags/#enable-tab-audio-muting
chrome://flags/#allow-previews
chrome://flags/#enable-app-banners
chrome://flags/#enable-experimental-app-banners
chrome://flags/#enable-md-extensions
chrome://flags/#enable-token-binding
chrome://flags/#enable-scroll-anchoring
chrome://flags/#enable-scroll-anchor-serialization
chrome://flags/#PasswordExport
chrome://flags/#PasswordImport
chrome://flags/#enable-google-branded-context-menu
chrome://flags/#remove-navigation-history
chrome://flags/#important-sites-in-cbd
chrome://flags/#enable-font-cache-scaling
chrome://flags/#new-audio-rendering-mixing-strategy
chrome://flags/#disable-background-video-track
chrome://flags/#expensive-background-timer-throttling
chrome://flags/#enable-new-print-preview
chrome://flags/#enable-desktop-ios-promotions
chrome://flags/#omnibox-rich-entity-suggestions
chrome://flags/#omnibox-tab-switch-suggestions
chrome://flags/#enable-new-app-menu-icon
chrome://flags/#enable-speculative-service-worker-start-on-query-input
chrome://flags/#memory-ablation
chrome://flags/#omnibox-ui-show-suggestion-favicons
chrome://flags/#enable-picture-in-picture
chrome://flags/#click-to-open-pdf
chrome://flags/#enable-parallel-downloading
chrome://flags/#pdf-isolation
chrome://flags/#ntp-ui-md
chrome://flags/#ntp-icons
chrome://flags/#ntp-backgrounds
chrome://flags/#enable-experimental-productivity-features
chrome://flags/#enable-lazy-frame-loading
chrome://flags/#site-settings
chrome://flags/#overscroll-history-navigation
chrome://flags/#lcd-text-aa
chrome://flags/#enable-desktop-pwas
chrome://flags/#enable-desktop-pwas-link-capturing
chrome://flags/#omnibox-new-answer-layout
chrome://flags/#enable-experimental-productivity-features

This had absolutely no effect on the dang flash, but the browser generally renders crazy fast/better.

I made a video of what I am seeing.  Rather than a screen recorder, I filmed it with phone.  I realize there is already video posted, but I figure more data can't hurt.

https://photos.app.goo.gl/r8bKXaDh6fxPxhW88

Is there any activity on this problem?

Is chrishtr still an active entity?

Yes I am here.

Ah, alright.  I am just trying to get some kind of idea what is going on with this issue.

I tried the "noflashing.ahk" approach I found in searching on google. It didn't help when loading a newtab page that had a custom newtab page. When duplicating a tab it stayed black. However newtab page (using Toby currently) it fails to work. Will watch for any relevant updates as I'm not clear on any other approach I can take with Chrome now that custom.css is not supported as previous solutions used.

Any updates on this? I have had to switch users with photosensitive epilepsy over to firefox.

I can confirm Version 70.0.3538.45 (Official Build) beta (64-bit) still has it.
I can confirm Version 71.0.3569.0 (Official Build) dev (64-bit) still has it.
I can confirm Version 71.0.3573.0 (Official Build) canary (64-bit) still has it.

I have found no solutions to this that (still?) work.
I have heard absolutely no updates to this bug.

I have new information to add as to potential cause/trigger.

Flashing problem occurs:
1) Log in to reddit, opt in to redesign, enable night mode.
2) Open several reddit posts in other background tabs.
3) Allow them to load fully.
4) Switch to the new tabs.  Upon first view, you get the brilliant white flash.

Flashing problem DOES NOT OCCUR:
1) Log in to reddit, OPT OUT of redesign.
2) Make sure you are actually opted out and viewing original reddit site design.
3) Install Reedit Enhancement Suite extention - https://chrome.google.com/webstore/detail/reddit-enhancement-suite/kbmfpngjjgdllneeigpgjifpgocmfgmb
4) With RES installed, in the top right of reddit, click the gear icon and enable night mode.  This is RES's night mode.
5) Now that this is set up, open some reddit posts in background tabs.
6) Allow the tabs to load fully.
7) There should be no white flash on first view.

NOTES:
It is nearly 5am, and I just came across this by chance.  While this successful test case does involve an extension, it is the first time I have come across no flash.

Also note that I have just updated to Version 70.0.3538.67 (Official Build) (64-bit) and have confirmed the steps in my last post are still fully applicable.

Also of note, I have confirmed that without logging in to Reddit, using new design, using night mode, no extensions, I get the white flash on first view in:

Version 70.0.3538.67 (Official Build) beta (64-bit)
Version 71.0.3578.10 (Official Build) dev (64-bit)
Version 72.0.3588.0 (Official Build) canary (64-bit)

Chrishtr, if you are unable to give this bug and related feedback attention, could you please allow bug ownership to pass to another?

The lack of responses and updates even to the base bug info is becoming a problem.  There is user reporting this as serious accessibility issue with users with photosensitive epilepsy.  There has been much information provided, including possible hint as to why this occurs and how to fix it (Comment 23).  If any further information might help, I would be happy to provide it.  Thanks.

+samans@ whom worked on the fix for related  issue 834449 . Per comment #23 this appears to be a similar issue with extensions involved.

Could you take a look, or help triage this?