Brave-browser: [Desktop] Brave somewhat crashes after machine wakes up from suspend

[kbsali]

Description

Since v1.13.82 (I am now running v1.13.86) Brave "sort of" crashes when waking up my computer after a suspend (on my laptop, when opening the lid after closing it :)).
I use "sort of crashes" because the windows are still opened but they all show a black screen and I can only see part of the tab but no other button/ui element what so ever (see screenshot below).
I am running Ubuntu Mate 20.04, but a colleague of mine has the exact same issue on Elementary 5.1.7 (based on Ubuntu 18.04).
Killing & restarting brave "fixes" the issue.

Steps to Reproduce

1. suspend Linux (close your laptop lid)
2. wake-up (open your laptop lid)

Actual result:

Expected result:

Brave should run as usual! :sweat_smile:

Reproduces how often:

Always

Brave version (brave://version info)

(also happening on 1.13.82)

Brave | 1.13.86 Chromium: 85.0.4183.102 (Official Build) (64-bit)

-- | --
Revision | ffe848af6a5df4fa127e2929331116b7f9f1cb30-refs/branch-heads/4183@{#1770}
OS | Linux
JavaScript | V8 8.5.210.20
Flash | (Disabled)
User Agent | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36
Command Line | /opt/brave.com/brave/brave --enable-dom-distiller --disable-domain-reliability --no-pings --extension-content-verification=enforce_strict --extensions-install-verification=enforce --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --enable-features=AutoupgradeMixedContent,PassiveMixedContentWarning,DnsOverHttps,OmniboxContextMenuShowFullUrls,MixedContentSiteSetting,WebUIDarkMode,PasswordImport,ReducedReferrerGranularity,PrefetchPrivacyChanges --disable-features=NotificationTriggers,TextFragmentAnchor,SafeBrowsingEnhancedProtection,AutofillEnableAccountWalletStorage,AllowPopupsDuringPageUnload,TabHoverCards,SmsReceiver,PrivacySettingsRedesign,VideoPlaybackQuality,AutofillServerCommunication,PasswordCheck --flag-switches-begin --load-media-router-component-extension=1 --flag-switches-end
Executable Path | /opt/brave.com/brave/brave
Profile Path | /home/kevin/.config/BraveSoftware/Brave-Browser/Profile 1

Version/Channel Information:

• Can you reproduce this issue with the current release?
  
  
  
  • yes
  
  
• Can you reproduce this issue with the beta channel?
  
  
  
  • yes (Brave Browser 85.1.15.46 beta)
  
  
• Can you reproduce this issue with the nightly channel?
  
  
  
  • YES (Chromium 85.0.4183.102 snap) !!!
  
  

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields?
• Does the issue resolve itself when disabling Brave Rewards?
• Is the issue reproducible on the latest version of Chrome?
  
  
  
  • YES (Chromium 85.0.4183.102 snap) !!!
  
  

Miscellaneous Information:

Just checked with the same colleague of mine, he has Chromium v84 and it works as expected.
So the issue seems to come from the version of Chromium Brave is based on, right?

Thanks for you help

[kbsali]

see related bug https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894432

[howdev]

I can confirm this on V1.14.84 with chromium 85. It is not crash as described. Is actually corrupted display.
Corrupted display with black screen in the browser after hibernate or suspend.

I found the fix is to enable Vulkan flag. The problem is gone.

[howdev]

But the Vulkan flag causes browser to lag

[howdev]

I tried the new release Brave 1.15.72 chromium 86. still same problem. I tried Beta channel also same problem
When you end the Brave gpu process, it restarts itself, then the UI returns to normal

[howdev]

I have a workaround, thanks to Linux ability.
use hibernate, suspend hook
write a script in here /lib/systemd/system-sleep
it is important to use HUP signal otherwise the gpu process won't work

!/bin/sh

case "$1" in
post)
pkill -HUP -f type=gpu
;;
esac

[jaubin]

Same there, but it worsens with Brave 86 at least with KDE :

• If the window is maxed out before suspending, after resuming transparency effects are completely broken on the whole desktop, and the only workaround is to log out/log in.

I see it occuring with NVidia drivers, but it seems that when using Mesa drivers the problem does not appear.

[howdev]

@jaubin Use systemd hibernate suspend hook. works fine with it. The issue seemed to do with Chromium as it renders the whole UI in its own toolkit and not Gtk or Qt.

[kbsali]

As far as I'm concerned, it's been working correctly ever since I updated the menu command to execute : /usr/bin/brave-browser-stable --use-gl=desktop %U

[howdev]

@kbsali brave browser does not have any commandline options

[kbsali]

does it not "inherit" the options of chromium

[howdev]

Command line is not related to the engine. you cannot use -help or ---help with brave, means there is no command options.

[kbsali]

No offense, but you can pass parameters to the brave executable, see man brave-browser-stable for the available options (and funny enough, the options are exactly the same as for chromium chromium --help).
Some of the options are not documented here though (--use-gl being one for them).

[howdev]

@kbsali that is strange implementation without listing in ---help. ---use-gl does work but not convenient to launch Brave. Someone suggested there is conf to put the flags. or you can find the same option in the chrome://flags. Either way, as long there is a workaround

[rebron]

possibly related to: https://bugs.chromium.org/p/chromium/issues/detail?id=791913

[JohnGalt1717]

I'm also getting this on Ubuntu 20.04 with Nvidia graphics and latest proprietary drivers.

Chrome on same machine doesn't have it.

[howdev]

@JohnGalt1717 That is strange. It is not just the browser window that is corrupted, it is the whole UI. So it should happen on Chrome too. Everything, the rendering and UI are done by Chromium

[jaubin]

Yes and when you switch from tab to tab you can see that actually the tabs become some kind of "transparent" on white backgrounds.
Le mardi 20 octobre 2020 à 02:01:15 UTC+2, howdev [e-mail] a écrit :

@JohnGalt1717 That is strange. It is not just the browser window that is corrupted, it is the whole UI. So it should happen on Chrome too. Everything, the rendering and UI are done by Chromium

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[JohnGalt1717]

For me, the page itself renders fine after a while (parts missing at first but a simple scroll fixes it). It's just the chrome on the outside. Edge dev on linux also works fine recovering from standby.

[ripekern]

I was having this difficulty and found the solution is go to settings in the brave-browser and disable hardware-acceleration. [ settings > system > Use hardware acceleration when available > OFF ]