Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

New windows are just white for a bit. #8128

Closed
lucidNTR opened this issue Apr 8, 2017 · 27 comments
Closed

New windows are just white for a bit. #8128

lucidNTR opened this issue Apr 8, 2017 · 27 comments

Comments

@lucidNTR
Copy link
Contributor

lucidNTR commented Apr 8, 2017

Test plan

#11764 (comment)


  • 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:

bildschirmfoto 2017-04-08 um 14 18 04

#3025

@cndouglas cndouglas added the perf label Apr 8, 2017
@AaronNGray
Copy link

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

@AaronNGray
Copy link

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

@jonathansampson
Copy link
Collaborator

@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
Copy link

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
Copy link

AaronNGray commented Apr 9, 2017

Debian GNU/Linux 8 (jessie) 64-bit - AMD Phenom(tm) 9650 Quad-Core Processor × 4 - 7.7 GiB
screenshot from 2017-04-09 18 48 44

@jonathansampson
Copy link
Collaborator

@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
Copy link

@jonathansampson I cloned master and followed the default instructions.

@AaronNGray
Copy link

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

> brave@0.14.1 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
Copy link

And on Windows the console displays this :-

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

> brave@0.13.5 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
Copy link
Collaborator

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
Copy link

AaronNGray commented Apr 13, 2017 via email

@jonathansampson
Copy link
Collaborator

@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
Copy link

AaronNGray commented Apr 14, 2017 via email

@jonathansampson
Copy link
Collaborator

@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
Copy link

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

Brave: 0.14.1
rev: 3de60d5
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
Copy link
Collaborator

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

@EricGrahamMacEachern
Copy link

@jonathansampson No the console is also completely white.

@luixxiul
Copy link
Contributor

luixxiul commented May 4, 2017

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
Copy link
Contributor

luixxiul commented May 4, 2017

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

@bsclifton
Copy link
Member

bsclifton commented May 9, 2017

I believe the original issue (seeing white for a bit) is well captured with #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

@bsclifton bsclifton added duplicate Issue has already been reported and removed needs-triage labels May 9, 2017
@luixxiul
Copy link
Contributor

luixxiul commented May 9, 2017

@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
Copy link
Contributor

luixxiul commented May 9, 2017

STR by @lucidNTR

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

@bsclifton
Copy link
Member

bsclifton commented May 9, 2017

@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?)

@bsclifton bsclifton reopened this May 9, 2017
@cezaraugusto
Copy link
Contributor

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

petemill added a commit that referenced this issue Nov 21, 2017
Separates parsing of APP_NEW_WINDOW action properties, and window creation / visibility logic.
Moves window creation logic to windows API.
Creates tests for existing APP_NEW_WINDOW action handler logic in windowsReducer
Creates tests for new windows.createWindow logic
Fixes test for downloadsReducer with not restoring a stub required by windowsReducer test

Fix #8128
petemill added a commit that referenced this issue Nov 21, 2017
Separates parsing of APP_NEW_WINDOW action properties, and window creation / visibility logic.
Moves window creation logic to windows API.
Creates tests for existing APP_NEW_WINDOW action handler logic in windowsReducer
Creates tests for new windows.createWindow logic
Fixes test for downloadsReducer with not restoring a stub required by windowsReducer test

Fix #8128
petemill added a commit that referenced this issue Nov 22, 2017
Separates parsing of APP_NEW_WINDOW action properties, and window creation / visibility logic.
Moves window creation logic to windows API.
Creates tests for existing APP_NEW_WINDOW action handler logic in windowsReducer
Creates tests for new windows.createWindow logic
Fixes test for downloadsReducer with not restoring a stub required by windowsReducer test

Fix #8128
petemill added a commit that referenced this issue Nov 22, 2017
Separates parsing of APP_NEW_WINDOW action properties, and window creation / visibility logic.
Moves window creation logic to windows API.
Creates tests for existing APP_NEW_WINDOW action handler logic in windowsReducer
Creates tests for new windows.createWindow logic
Fixes test for downloadsReducer with not restoring a stub required by windowsReducer test

Fix #8128
@bsclifton bsclifton modified the milestones: 0.19.x Hotfix 6 (Release channel), 0.20.x (Beta Channel) Nov 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.