Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ozone platform Wayland causes 1 minute startup delay #39815

Closed
1 of 6 tasks
CarloCattano opened this issue Jul 17, 2024 · 1 comment
Closed
1 of 6 tasks

Ozone platform Wayland causes 1 minute startup delay #39815

CarloCattano opened this issue Jul 17, 2024 · 1 comment

Comments

@CarloCattano
Copy link

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.

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

  1. launch brave with the use ozone flags and wayland
  2. wait 50+ seconds

Actual result

  1. brave shows up with broken restored tabs mostly (graphical glitches)

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

  • release (stable)
  • beta
  • nightly

Reproducibility

  • with Brave Shields disabled
  • with Brave Rewards disabled
  • in the latest version of Chrome

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

@CarloCattano
Copy link
Author

sent twice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant