Browser-laptop: New windows are just white for a bit.

[lucidNTR]

Test plan

https://github.com/brave/browser-laptop/pull/11764#issue-270588807

---

• Did you search for similar issues before submitting this one?
  yes

• Describe the issue you encountered:
  Opening new windows show chromeless completely white before the window frame etc are loaded.
  This gives me a feeling of beeing not solid software and reminds me of 'badly packaged electron webapps'. I thought this was just due to me using webpack watch mode but i was shocked to see this is the behaviour in the release version too.

• Platform (Win7, 8, 10? macOS? Linux distro?):
  mac os

• Brave Version (revision SHA):
  Brave 0.14.2
  rev 10539c2 and before

• Steps to reproduce:

  1. start brave
  2. open new window
  3. stare at a white, completely chromeless window for fractions of a second

• Actual result:
  i see a white square

• Expected result:
  i see a browser window

• Will the steps above reproduce in a fresh profile? If not what other info can be added?
  yes

• Is this an issue in the currently released version?
  yes

• Can this issue be consistently reproduced?
  yes

• Screenshot if needed:
  

3025

[AaronNGray]

I am getting permanent white window on Windows 10 with Node v7.8.0

[AaronNGray]

Getting simular on Linux as on windows but with a menu and window title.

[jonathansampson]

@AaronNGray Could you share a screenshot of what you're seeing from both Windows 10, and Linux? Your report sounds different from this issue (since your white-window persists).

[AaronNGray]

On Windows 10 it is a featureless white full screen window with no borders. I will do a screen shot for Linux when in a bit.

[AaronNGray]

Debian GNU/Linux 8 (jessie) 64-bit - AMD Phenom(tm) 9650 Quad-Core Processor × 4 - 7.7 GiB

[jonathansampson]

@AaronNGray You appear to be running a preview build of Brave (presence of a Debug menu). Which version of Brave are you presently testing? 0.14.2 Preview? Can you press Shift+F8 and see if there is any output in the Console?

[AaronNGray]

@jonathansampson I cloned master and followed the default instructions.

[AaronNGray]

On Linux pressing Shift-F8 gives me developers mode panel on left hand side

I am getting this output on the console I should have posted :-

aaronngray@aarongray:~/GitHub/browser-laptop$ npm start

> [email protected] start /home/aaronngray/GitHub/browser-laptop
> node ./tools/start.js --user-data-dir=brave-development --debug=5858 --enable-logging --v=0 --enable-extension-activity-logging --enable-sandbox-logging --enable-dcheck --no-sandbox

Gtk-Message: Failed to load module "canberra-gtk-module"
[13121:13121:0409/232221.159922:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
Crash reporting enabled

[AaronNGray]

And on Windows the console displays this :-

C:\Users\aaron\GitHub\browser-laptop>npm start

> [email protected] start C:\Users\aaron\GitHub\browser-laptop
> node ./tools/start.js --user-data-dir=brave-development --debug=5858 --enable-logging --v=0 --enable-extension-activity-logging --enable-sandbox-logging --enable-dcheck

[24236:17364:0409/225134.810:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
Crash reporting enabled
{ version: '0.14.1',
  name: 'Brave 0.14.1',
  pub_date: '2017-04-01T06:00:15.036Z',
  notes: 'Fixed a copy and paste issue, fixed the lion badge position, and improved security. More details: https://github.com/brave/browser-laptop/releases/tag/v0.14.1dev\n\nAdded ability to see SSL certificates, added 100 tabs per tab set, added lion icon badge, fixed keyboard shortcuts, fixed YouTube ad blocking, and fixed many other issues. More details: https://github.com/brave/browser-laptop/releases/tag/v0.14.0dev' }

[jonathansampson]

Thank you, @AaronNGray. We'll be looking specifically at performance issues in the very near future. I appreciate your assistance in providing this helpful feedback!

[AaronNGray]

I cloned from master.

On 9 April 2017 at 20:20, Jonathan Sampson [e-mail] wrote:

@AaronNGray https://github.com/AaronNGray You appear to be running a
preview build of Brave (presence of a Debug menu). Which version of Brave
are you presently testing? 0.14.2 Preview? Can you press Shift+F8 and see
if there is any output in the Console?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brave/browser-laptop/issues/8128#issuecomment-292806570,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFOEw66BQV_IiK1VM-P6Yty-0O76Pknks5ruS-PgaJpZM4M3r-a
.

--
Aaron Gray

Independent Open Source Software Engineer, Computer Language Researcher,
Information Theorist, and amateur computer scientist.

[jonathansampson]

@AaronNGray That is what I assumed; we'll be dumping some performance improvements into master before too long. Thank you for helping us keep an eye on things :)

[AaronNGray]

Its not just a performance issue, the white screen/widnow is permanent. I
should have raised it as another separate issue.

I was trying to build Brave so would appreciate how to get it to work which
release to use.

On 14 April 2017 at 00:55, Jonathan Sampson [e-mail]
wrote:

@AaronNGray https://github.com/AaronNGray That is what I assumed; we'll
be dumping some performance improvements into master before too long. Thank
you for helping us keep an eye on things :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brave/browser-laptop/issues/8128#issuecomment-294050593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFOE7nPV1L-RWntqjuAfh0ok3Vbc9cKks5rvrXfgaJpZM4M3r-a
.

--
Aaron Gray

Independent Open Source Software Engineer, Computer Language Researcher,
Information Theorist, and amateur computer scientist.

[jonathansampson]

@AaronNGray Ah, sorry for the confusion. I happened to have been looking at a performance-related issue that manifested itself as a white screen. My contexts were muddled-up. Please excuse my ignorance :)

If you like, we can hop on a call via Skype or Google Hangouts and look into the issue you're facing.

[EricGrahamMacEachern]

I am getting a permanent white window on Ubuntu 16.04 for new tabs.

Brave: 0.14.1
rev: 3de60d52df3ef48d12d9696a076b72079beb9658
Muon: 2.57.8
libchromiumcontent: 57.0.2987.133
V8: 5.7.492.71
Node.js: 7.4.0
Update Channel: dev
os.platform: linux
os.release: 4.4.0-72-generic
os.arch: x64

[jonathansampson]

@EricGrahamMacEachern Can you press Shift+F8 and report any output in the browser's console?

[EricGrahamMacEachern]

@jonathansampson No the console is also completely white.

[luixxiul]

Opening new windows show chromeless completely white before the window frame etc are loaded.

I notice the issue on the PC which is relatively new (bought a half year ago). The window is blank for several seconds. Lately I started noticing the issue more often after the function to detach tabs was implemented.

[luixxiul]

I added the needs-triage label just now. Please add a milestone and labels if necessary, thanks.

[bsclifton]

I believe the original issue (seeing white for a bit) is well captured with https://github.com/brave/browser-laptop/issues/5309

When the screen is completely white, we have some steps in our wiki you can try:
https://github.com/brave/browser-laptop/wiki/Troubleshooting#window-is-solid-black-or-solid-white-looks-like-a-blank-page

~I'm going to close this issue as a dupe~

[luixxiul]

@bsclifton I thought the issues were bit different; blank new tabs (which load images) vs blank new windows (which do not load images but data-reactroot). I assumed that the latter was the problem here, as the 1st post by @lucidNTR. The other issue (AMD driver compatibility) above is the duplicate.

[luixxiul]

STR by @lucidNTR

1. start brave
2. open new window
3. stare at a white, completely chromeless window for fractions of a second

[bsclifton]

@luixxiul good call- I missed the part about new window (I think I wrongly read it as new tab)

Let's reopen this issue 😄

The root cause will likely be similar. Chromium has a default of white for the web contents when it's created, IIRC. We should determine what we want this to look like (keep as white, fade in? default to black?)

[lucidNTR]

@bsclifton maybe there is a confusion again, my original ticket was not about the white background per se but about the completely missing tab bar + any expected window 'chrome'.
the expected behaviour, also what chrome and safari etc. show is to not display windows at all until the interface elements are ready.

[lucidNTR]

i would like to help here but i dont understand the exact pipeline of all the init events etc that need to be done before the window could be displayed and how to determine the exact time all events are done, also we probably need to take a few init shortcuts to make window opening seem instant

[luixxiul]

CC @cezaraugusto for including this issue to the task list of the perf improvement project

[cezaraugusto]

^ ya this is a big one I'm including it in there