Chrome starts very slowly on Wayland

Juhayer Al Wasif · 2024-08-15 18:18:22

Here is the terminal output when launching google-chrome-stable:

google-chrome-stable
Created TensorFlow Lite XNNPACK delegate for CPU.
[119358:1:0816/000113.236360:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119192:11:0816/000113.236516:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119154:1:0816/000113.236612:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119200:11:0816/000113.236454:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119058:119058:0816/000113.242366:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[119609:1:0816/000143.428208:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119358:1:0816/000143.428726:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[119192:11:0816/000143.428732:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[119058:119058:0816/000143.435333:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[119058:119058:0816/000143.873123:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.", source: https://ogs.google.com/u/0/widget/app?eom=1&awwd=1&gm3=1&origin=chrome-untrusted%3A%2F%2Fnew-tab-page&origin=chrome%3A%2F%2Fnew-tab-page&cn=app&pid=1&spid=243&hl=en&dm= (0)
[119192:11:0816/000213.626188:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[119058:119058:0816/000213.632881:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[119192:11:0816/000213.788767:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119155:7:0816/000213.788814:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[119154:7:0816/000213.788780:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[120860:120860:0816/000213.813321:ERROR:gl_utils.cc(424)] [.WebGL-0x3570004b0e00]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[120860:120860:0816/000213.850994:ERROR:gl_utils.cc(424)] [.WebGL-0x3570004b0e00]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[120860:120860:0816/000213.869641:ERROR:gl_utils.cc(424)] [.WebGL-0x3570004b0e00]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[119058:119058:0816/000214.015915:ERROR:CONSO
LE(0)] "Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received", source: https://ogs.google.com/u/0/widget/app?eom=1&awwd=1&gm3=1&origin=chrome-untrusted%3A%2F%2Fnew-tab-page&origin=chrome%3A%2F%2Fnew-tab-page&cn=app&pid=1&spid=243&hl=en&dm= (0)
[119104:119117:0816/000215.946912:ERROR:ssl_client_socket_impl.cc(883)] handshake failed; returned -1, SSL error code 1, net_error -101

And then chrome launches after a while

Last edited by Juhayer Al Wasif (2024-08-15 18:19:00)

Trilby · 2024-08-15 18:24:58

What wayland compositor is this under? What flags do you have in your chrome-flags.conf? If none, is it even starting on wayland? I think the default without flags is to run in X11 mode which may be triggering a start of Xwayland.

Also, is it slow launching a second instance, or just the first?

Last edited by Trilby (2024-08-15 18:25:24)

Juhayer Al Wasif · 2024-08-15 19:08:09

It is under hyprland compositor.

I only have this chrome flag enabled : Preferred Ozone platform- Wayland.

It is slow launching on every instance.

seth · 2024-08-15 19:59:43

google-chrome-stable

How does chomrium behave?
And xdg-desktop-portal errors/warnings in your journal?

Juhayer Al Wasif · 2024-08-15 20:23:24

Chromium behaves fine except for the very slow starting time on each instance.

 journalctl
Jul 31 17:52:39 envy systemd-xdg-autostart-generator[994]: Configuration file /home/wasif/.config/autostart/windscribe.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Jul 31 17:52:39 envy systemd[987]: Queued start job for default target Main User Target.
Jul 31 17:52:39 envy systemd[987]: Created slice User Application Slice.
Jul 31 17:52:39 envy systemd[987]: Reached target Paths.
Jul 31 17:52:39 envy systemd[987]: Reached target Timers.
Jul 31 17:52:39 envy systemd[987]: Starting D-Bus User Message Bus Socket...
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG network certificate management daemon.
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 31 17:52:39 envy systemd[987]: Listening on GnuPG public key management service.
Jul 31 17:52:39 envy systemd[987]: Listening on p11-kit server.
Jul 31 17:52:39 envy systemd[987]: Listening on PipeWire PulseAudio.
Jul 31 17:52:39 envy systemd[987]: Listening on PipeWire Multimedia System Sockets.
Jul 31 17:52:39 envy systemd[987]: Listening on D-Bus User Message Bus Socket.
Jul 31 17:52:39 envy systemd[987]: Reached target Sockets.
Jul 31 17:52:39 envy systemd[987]: Reached target Basic System.
Jul 31 17:52:39 envy systemd[987]: Starting Update XDG user dir configuration...
Jul 31 17:52:39 envy systemd[987]: Finished Update XDG user dir configuration.
Jul 31 17:52:39 envy systemd[987]: Reached target Main User Target.
Jul 31 17:52:39 envy systemd[987]: Startup finished in 155ms.
Jul 31 17:52:44 envy systemd[987]: Created slice User Core Session Slice.
Jul 31 17:52:44 envy systemd[987]: Starting D-Bus User Message Bus...
Jul 31 17:52:44 envy dbus-broker-launch[1077]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jul 31 17:52:44 envy dbus-broker-launch[1077]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jul 31 17:52:44 envy dbus-broker-launch[1077]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jul 31 17:52:44 envy dbus-broker-launch[1077]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jul 31 17:52:44 envy systemd[987]: Started D-Bus User Message Bus.
Jul 31 17:52:44 envy dbus-broker-launch[1077]: Ready
Jul 31 17:52:45 envy systemd[987]: Starting User preferences database...
Jul 31 17:52:45 envy systemd[987]: Started User preferences database.
Jul 31 17:52:45 envy systemd[987]: Starting Accessibility services bus...
Jul 31 17:52:45 envy systemd[987]: Started Accessibility services bus.
Jul 31 17:52:45 envy at-spi-bus-launcher[1304]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +15: Eavesdropping is deprecated and ignored
Jul 31 17:52:45 envy at-spi-bus-launcher[1304]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +17: Eavesdropping is deprecated and ignored
Jul 31 17:52:45 envy dbus-broker-launch[1304]: Ready
Jul 31 17:52:45 envy systemd[987]: Created slice Slice /app/dbus-:1.29-org.a11y.atspi.Registry.
Jul 31 17:52:45 envy systemd[987]: Started dbus-:1.29-org.a11y.atspi.Registry@0.service.
Jul 31 17:52:45 envy systemd[987]: Starting Portal service...
Jul 31 17:52:45 envy at-spi2-registryd[1306]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 31 17:52:45 envy systemd[987]: Starting flatpak document portal service...
Jul 31 17:52:45 envy systemd[987]: Starting sandboxed app permission store...
Jul 31 17:52:45 envy systemd[987]: Started sandboxed app permission store.
Jul 31 17:52:45 envy systemd[987]: Started flatpak document portal service.
Jul 31 17:52:45 envy systemd[987]: Starting Portal service (GTK/GNOME implementation)...
Jul 31 17:52:45 envy systemd[987]: Started PipeWire Multimedia Service.
Jul 31 17:52:45 envy systemd[987]: Started Multimedia Service Session Manager.
Jul 31 17:52:45 envy systemd[987]: Started PipeWire PulseAudio.
Jul 31 17:52:45 envy systemd[987]: Started Portal service (GTK/GNOME implementation).
Jul 31 17:52:45 envy systemd[987]: Starting Portal service (Hyprland implementation)...
Jul 31 17:52:45 envy systemd[987]: Started Portal service (Hyprland implementation).
Jul 31 17:52:45 envy systemd[987]: Started Portal service.
Jul 31 17:52:45 envy wireplumber[1361]: [0:00:24.819295134] [1361] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Jul 31 17:52:45 envy wireplumber[1361]: [0:00:24.819313920] [1361] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info

Last edited by Juhayer Al Wasif (2024-08-15 20:25:10)

seth · 2024-08-15 20:27:51

The point was that your OP wasn't abotu chromium but maybe https://aur.archlinux.org/packages/google-chrome or some flatpak - https://archlinux.org/packages/extra/x86_64/chromium/ behaves exactly the same?

That's one random page of the journal, try

sudo journalctl -b | curl -F 'file=@-' 0x0.st

*after* starting chromium/chrome and maybe have a look at it yourself, too

Juhayer Al Wasif · 2024-08-15 20:34:29

sudo journalctl -b | curl -F 'file=@-' 0x0.st
[sudo] password for wasif:

curl: option -F: is badly used here
curl: try 'curl --help' for more information

WorMzy · 2024-08-15 20:39:56

Mod note: Moving to AUR Issues.

seth · 2024-08-15 20:40:08

Typo?
Fish?

cat /proc/$$/cmdline

Juhayer Al Wasif · 2024-08-15 20:44:52

Yes, I am using fish.

 cat /proc/$$/cmdline
fish: $$ is not the pid. In fish, please use $fish_pid.
cat /proc/$$/cmdline
           ^

seth · 2024-08-15 20:49:04

Try a big boy shell or

sudo journalctl -b > /tmp/journal.txt
curl -F'file=@/tmp/journal.txt'

Juhayer Al Wasif · 2024-08-15 20:52:44

sudo journalctl -b > /tmp/journal.txt
  curl -F'file=@/tmp/journal.txt'
[sudo] password for wasif:
curl: (2) no URL specified
curl: try 'curl --help' for more information

seth · 2024-08-15 20:55:22

"curl -F'file=@/tmp/journal.txt' https://0x0.st" - sorry, but also try to read the actual output.

Juhayer Al Wasif · 2024-08-15 20:56:59

curl -F'file=@/tmp/journal.txt' https://0x0.st
<html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>

seth · 2024-08-15 21:19:22

du -h /tmp/journal.txt

Either way, figure a way to upload your journal or this isn't going anyway.
Consider using a real shell and re-try #6

Trilby · 2024-08-15 21:29:12

While the journal is important, another test that can be done while you work on that is testing 1) another compositor (I'd suggest sway) and 2) an Xorg session. Is it similarly slow under those conditions?

Juhayer Al Wasif · 2024-08-16 05:58:57

journalctl: https://pastebin.com/hYTjEe9F

Juhayer Al Wasif · 2024-08-16 06:00:26

I have tested it on Xorg season, chrome is running perfectly fine there.

seth · 2024-08-16 07:50:39

That is, again, one page out of the journal
From july 31th

bash
sudo journalctl -b | curl -F 'file=@-' 0x0.st # verbatim

I guess there's a massive language barrier and you're trying to do this via google translate. Don't.
https://www.deepl.com/translator#en/ar/Foo

I have tested it on Xorg season, chrome is running perfectly fine there.

You've still not identified the actual process.
And have you tried CHROMIUM, like the actual https://archlinux.org/packages/extra/x86_64/chromium/ on some wayland instance?

Juhayer Al Wasif · 2024-08-16 13:38:48

So I need to install another wayland compositor to check it the problem persists?

bash
[wasif@envy ~]$ sudo journalctl -b | curl -F 'file=@-' 0x0.st # verbatim
[sudo] password for wasif:
curl: option -F: is badly used here
curl: try 'curl --help' for more information

Last edited by Juhayer Al Wasif (2024-08-16 13:39:31)

seth · 2024-08-16 13:44:35

I just tried and the redirection actually works in fish - I've no idea what you're typing there…

type -a curl

And no, you need to test chromium, NOT! chrome.

Juhayer Al Wasif · 2024-08-16 13:53:51

type -a curl
curl is /usr/bin/curl

seth · 2024-08-16 14:17:21

Do you copy-paste the command or type it by hand?
Because you'd get the error when eg. using upticks instead of single quotes

echo foo | curl -F `file=@-` 0x0.st # bad
echo foo | curl -F 'file=@-' 0x0.st # good

Juhayer Al Wasif · 2024-08-16 15:34:14

copy paste.

BTW, I just found out disabling Discrete graphics fixes the problem.

seth · 2024-08-16 15:58:42

Misconfigured Nvidia falling back to Zink does this, i'll tell you If we ever get to se a journal.

Arch Linux

#1 2024-08-15 18:18:22

Chrome starts very slowly on Wayland

#2 2024-08-15 18:24:58

Re: Chrome starts very slowly on Wayland

#3 2024-08-15 19:08:09

Re: Chrome starts very slowly on Wayland

#4 2024-08-15 19:59:43

Re: Chrome starts very slowly on Wayland

#5 2024-08-15 20:23:24

Re: Chrome starts very slowly on Wayland

#6 2024-08-15 20:27:51

Re: Chrome starts very slowly on Wayland

#7 2024-08-15 20:34:29

Re: Chrome starts very slowly on Wayland

#8 2024-08-15 20:39:56

Re: Chrome starts very slowly on Wayland

#9 2024-08-15 20:40:08

Re: Chrome starts very slowly on Wayland

#10 2024-08-15 20:44:52

Re: Chrome starts very slowly on Wayland

#11 2024-08-15 20:49:04

Re: Chrome starts very slowly on Wayland

#12 2024-08-15 20:52:44

Re: Chrome starts very slowly on Wayland

#13 2024-08-15 20:55:22

Re: Chrome starts very slowly on Wayland

#14 2024-08-15 20:56:59

Re: Chrome starts very slowly on Wayland

#15 2024-08-15 21:19:22

Re: Chrome starts very slowly on Wayland

#16 2024-08-15 21:29:12

Re: Chrome starts very slowly on Wayland

#17 2024-08-16 05:58:57

Re: Chrome starts very slowly on Wayland

#18 2024-08-16 06:00:26

Re: Chrome starts very slowly on Wayland

#19 2024-08-16 07:50:39

Re: Chrome starts very slowly on Wayland

#20 2024-08-16 13:38:48

Re: Chrome starts very slowly on Wayland

#21 2024-08-16 13:44:35

Re: Chrome starts very slowly on Wayland

#22 2024-08-16 13:53:51

Re: Chrome starts very slowly on Wayland

#23 2024-08-16 14:17:21

Re: Chrome starts very slowly on Wayland

#24 2024-08-16 15:34:14

Re: Chrome starts very slowly on Wayland

#25 2024-08-16 15:58:42

Re: Chrome starts very slowly on Wayland

Board footer