1.15 - Bug - Grey Screen with Vivaldi Icon
-
I just updated to 1.15, and when I open Vivaldi, for a few seconds everything is working fine (webpage, menu bar, panel), but then it changes to a grey screen with a big Vivaldi icon. I have attached a screenshot.
-
same issue here windows 8.1
had to downgrade to 1.14 which it works
which of course appears a message about the profile its the new version of vivaldi but even that works
-
On first restart after update, I got the same result.
I closed and restarted the browser, and all was fine.
However, please file a bug report.
-
@ayespy tried so many times it didnt works which it why i downgraded to 1.14, anyways i made a bug report too
-
@eilegz Were you trying to run it with your CSS modifications? Did you try it without?
-
@ayespy yes i did remove my css modification and its the same issue
-
@eilegz I'm still trying to reproduce it. Can't yet.
-
@eilegz Have you tried with a totally clean profile? refresh your profile
-
Just had the same thing at 1st start after update. (Ubuntu 14.04)
After closing the window, I had to manually kill some remaining "zombie" processes in order to start Vivaldi again. Then, it worked... -
I solved it deleting the GPUCache and Media Cache subfolders in the default folder.
-
@guilimote said in 1.15 - Bug - Grey Screen with Vivaldi Icon:
Just had the same thing at 1st start after update. (Ubuntu 14.04)
After closing the window, I had to manually kill some remaining "zombie" processes in order to start Vivaldi again. Then, it worked...@pesanur said in 1.15 - Bug - Grey Screen with Vivaldi Icon:
I solved it deleting the GPUCache and Media Cache subfolders in the default folder.
Tried these two but the bug still happens for the first window I open, no problem for second window and so on.
I don't want to reset profile unless really necessary. -
@christantoan Since you are the one that can reproduce all the time please run vivaldi with
--debug-packed-apps
. Then right-click on the grey window and choose Inspect. And let us know what errors you get under the Console tab. -
I fixed mine by logging out of Vivaldi Sync.
-
@an_dz said in 1.15 - Bug - Grey Screen with Vivaldi Icon:
@christantoan Since you are the one that can reproduce all the time please run vivaldi with
--debug-packed-apps
. Then right-click on the grey window and choose Inspect. And let us know what errors you get under the Console tab.Here's what I get:
@gwen-dragon said in 1.15 - Bug - Grey Screen with Vivaldi Icon:
That may something related to Sync.
As Sync is only tested/recommended for Snapshots yet (is experimental, only can be enabled in Experimental settings of Vivaldi.) you may see issues as such tab crashes with gray page.Yes, it seems like it's a Sync issue as the new window I open always start with notification that Sync has problem.
And disabling sync from the Experiments page fixed the problem. -
logged out from sync on the old version, and now after update seems that it works
-
@christantoan Thanks, I've added your screen into the bug tracker so the devs can take a look what's the problem with sync.
-
This happens randomly when opening a new window either by starting the browser, pressing ctrl-n, or a new window opened from JS or from a link. I am running vivaldi with --debug-packed-apps now for a couple of weeks, until now right-clicking the grey screen did not work, but now I could start the dev tools.
I doubt that this screenshot has useful information, what can I do better next time?
The errors seem to be from the dev tools.
-
Even better. Detaching a completely loaded page into a new window: 3min!
Seems that Vivaldi somehow gets blocked by included images. After the 4rd one finishes, other stuff is loaded (network view)The data dirs are located on a local SSD and my PC has sufficient memory to cache vivaldi data dirs a couple of times.
-
@eazrael Please report it at the bug tracker.
Explain what happens and when it happens and link those images in the report. Explain like you were talking with a 5 year old on how to reproduce, the more details you give the easier to reproduce.
Your bug is unrelated to the others in this thread as the original bug has already been mitigated and your error messages don't match with the older ones.
-
Okay. Will do.
Anecdote: when our customers explain us their issues, I have always the feeling I talk to 5 year old
-
-