You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using brave-browser-nightly --enable-features=UseOzonePlatform -ozone-platform=wayland
Brave takes at last +50 seconds to start.
Here is an example log of what happens during startup, and some additional bug on restore.
brave-browser-nightly --enable-features=UseOzonePlatform -ozone-platform=wayland
[40758:40758:0717/105521.352387:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.
[40758:40778:0717/105522.240051:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[40758:40758:0717/105551.437317:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[40758:40758:0717/105621.690315:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
# 1 minute later ..
# it opens
Even on mouse move in the restored page DOM produces numerous logs like this one ad infinitum:
[41608:41636:0717/105729.028663:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mail
[41608:41636:0717/105729.028728:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[41608:41636:0717/105729.028792:ERROR:shared_image_manager.cc(326)] SharedImageManager::ProduceMemory: Trying to Produce a Memory representation from a non-existent mailbox.
[41608:416
When the restored tabs appear, chances are they are going to get obscured by mysterious dark rectangles and behave strangely with the console spamming the mentioned shared image manager errors.
the only way out is to copy the restored tab url into a fresh new tab.
Steps to reproduce
launch brave with the use ozone flags and wayland
wait 50+ seconds
Actual result
brave shows up with broken restored tabs mostly (graphical glitches)
Description
when using
brave-browser-nightly --enable-features=UseOzonePlatform -ozone-platform=wayland
Brave takes at last +50 seconds to start.
Here is an example log of what happens during startup, and some additional bug on restore.
When the restored tabs appear, chances are they are going to get obscured by mysterious dark rectangles and behave strangely with the console spamming the mentioned shared image manager errors.
the only way out is to copy the restored tab url into a fresh new tab.
Steps to reproduce
Actual result
Expected result
A reasonably fast startup
Reproduces how often
Easily reproduced
Brave version (brave://version info)
1.69.111 Chromium: 127.0.6533.43 (Official Build) nightly (64-bit)
Channel information
Reproducibility
Miscellaneous information
Linux arch 6.9.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 12 Jul 2024 00:06:53 +0000 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: