Chrome starts very slowly on Wayland

Juhayer Al Wasif · 2024-08-16 16:07:41

Juhayer Al Wasif wrote:

journalctl: https://pastebin.com/hYTjEe9F

I have uploaded it here, is it something wrong here?

seth · 2024-08-16 16:11:09

seth wrote:

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

Edith: and yes, i noticed it should say 31st

Last edited by seth (2024-08-16 16:13:50)

Juhayer Al Wasif · 2024-08-16 16:12:58

so journalctl command is not enough. what exact command should I put to see todays's journal?

seth · 2024-08-16 16:15:27

I posted that multiple Times, for some reason you fudged the piped Upload and the temporary File you created exceeded the 0x0.st quota

Juhayer Al Wasif · 2024-08-16 16:34:02

I may upload them in the pastebin next time, so can please tell me the command again?

seth · 2024-08-16 18:13:59

No. You'll make the god damn effort to actually look at the commands I suggested before, understand them, spot an incredibly distinct pattern and then conclude this by yourself.
Or read https://wiki.archlinux.org/title/Systemd/Journal

Juhayer Al Wasif · 2024-08-16 19:10:31

https://pastebin.com/Qg4BcT8F

I hope this helps

seth · 2024-08-16 19:58:43

That's the first page of the jouranal…
"sudo journalctl -b > /tmp/journal.txt" and upload that file…

Juhayer Al Wasif · 2024-08-16 20:14:12

is this alright now?

https://termbin.com/f97r

seth · 2024-08-16 20:26:51

Your quota issues were likely because the journal is flooded w/

Aug 17 01:03:23 envy kernel: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Cannot create sg_table for NvKmsKapiMemory 0x00000000388b849b

There're more than 5000 events in one second.

The error doesn't show up a lot, https://forums.developer.nvidia.com/t/w … dec/215143 and you certainly want to check whether this is related to the chosen wayland compositor (reboot, don't start Hyprland and then try eg. sway or weston and see whether the error shows up) and then post your Hyprland config.

Also

pacman -Qikk nvidia nvidia-utils

The nvidia GPU doesn't show up as VGA device?

lspci

Last edited by seth (2024-08-16 20:27:04)

Juhayer Al Wasif · 2024-08-16 20:53:50

Hey, I have tested chromium on sway, It still opens with a long delay.

And here is my hyprland configs: https://file.io/XwgUgBbvfDar

command outputs: https://termbin.com/g5c8

Last edited by Juhayer Al Wasif (2024-08-16 20:58:09)

seth · 2024-08-16 21:01:06

https://file.io/XwgUgBbvfDar is deleted

0000:01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1)

In case you're trying to run Hyprland on the nvidia chip, don't - it's a mere 3D accelerator that you can invoke when playing a game or so, https://wiki.archlinux.org/title/PRIME# … figuration

Juhayer Al Wasif · 2024-08-16 21:15:36

https://github.com/Juhayer-Al-Wasif/hypr

I am not trying to run hyprland on nvidia. I just want to do general works on intel gpu and whenever I need nvidia like for gaming, only then I want to use it.

seth · 2024-08-16 21:27:30

What do you think https://github.com/Juhayer-Al-Wasif/hyp … vidia.conf does?
Skip that, try again.
Post the output of "glxinfo -B"

Juhayer Al Wasif · 2024-08-16 21:30:37

❯ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4096 MB
    Total available memory: 4096 MB
    Currently available dedicated video memory: 3720 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1650 Ti with Max-Q Design/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 555.58.02
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 555.58.02
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 555.58.02
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Last edited by Juhayer Al Wasif (2024-08-16 21:50:05)

seth · 2024-08-16 22:09:12

Yeah, you're running Hyprland on nvidia, likely because of the mentioned configlet.
Don't.

Juhayer Al Wasif · 2024-08-16 22:09:54

Do I just need to remove the nvidia.conf?

seth · 2024-08-16 22:10:39

I'd remove/comment the include in the hyprland.conf

Juhayer Al Wasif · 2024-08-16 22:16:31

I have commented the nvidia.conf line in hyprland.conf file. But still the delay persists.

Last edited by Juhayer Al Wasif (2024-08-16 22:18:35)

seth · 2024-08-16 22:23:48

And what does "glxinfo -B" now report?
Are you running on the intel chip?

Juhayer Al Wasif · 2024-08-16 22:29:56

❯ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49)
    Version: 24.1.6
    Accelerated: yes
    Video memory: 7873MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.6-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.6-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.6-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

yep, it's on intel.

seth · 2024-08-16 22:52:12

Are the nvidia GEM errors now gone?
Do they re-appear when starting chromium?
What does chromium say in about:gpu?

Oh, and you now *are* trying this on chromium and not some binary google-chrome release that might end up running on xwayland?
https://wiki.archlinux.org/title/Waylan … s_visually

Juhayer Al Wasif · 2024-08-17 06:22:35

chromium
[34559:1:0817/122021.036518:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[34490:34490:0817/122021.043549:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[34490:34490:0817/122051.270128:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[34490:34490:0817/122121.500294:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512
[34560:7:0817/122121.669952:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[34559:7:0817/122121.671028:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

nvidia GEM errors do not appears when starting chromium.

Last edited by Juhayer Al Wasif (2024-08-17 07:19:10)

Juhayer Al Wasif · 2024-08-17 06:30:48

While running chromium, I checked it with xorg-xclients. But there is nothing running in xwayland.

❯ xlsclients -l

~
❯

seth · 2024-08-17 07:14:36

Are the nvidia GEM errors now gone?
Do they re-appear when starting chromium?
What does chromium say in about:gpu?

and please don't bump - edit your previous post if nobody has yet replied.

Arch Linux

#26 2024-08-16 16:07:41

Re: Chrome starts very slowly on Wayland

#27 2024-08-16 16:11:09

Re: Chrome starts very slowly on Wayland

#28 2024-08-16 16:12:58

Re: Chrome starts very slowly on Wayland

#29 2024-08-16 16:15:27

Re: Chrome starts very slowly on Wayland

#30 2024-08-16 16:34:02

Re: Chrome starts very slowly on Wayland

#31 2024-08-16 18:13:59

Re: Chrome starts very slowly on Wayland

#32 2024-08-16 19:10:31

Re: Chrome starts very slowly on Wayland

#33 2024-08-16 19:58:43

Re: Chrome starts very slowly on Wayland

#34 2024-08-16 20:14:12

Re: Chrome starts very slowly on Wayland

#35 2024-08-16 20:26:51

Re: Chrome starts very slowly on Wayland

#36 2024-08-16 20:53:50

Re: Chrome starts very slowly on Wayland

#37 2024-08-16 21:01:06

Re: Chrome starts very slowly on Wayland

#38 2024-08-16 21:15:36

Re: Chrome starts very slowly on Wayland

#39 2024-08-16 21:27:30

Re: Chrome starts very slowly on Wayland

#40 2024-08-16 21:30:37

Re: Chrome starts very slowly on Wayland

#41 2024-08-16 22:09:12

Re: Chrome starts very slowly on Wayland

#42 2024-08-16 22:09:54

Re: Chrome starts very slowly on Wayland

#43 2024-08-16 22:10:39

Re: Chrome starts very slowly on Wayland

#44 2024-08-16 22:16:31

Re: Chrome starts very slowly on Wayland

#45 2024-08-16 22:23:48

Re: Chrome starts very slowly on Wayland

#46 2024-08-16 22:29:56

Re: Chrome starts very slowly on Wayland

#47 2024-08-16 22:52:12

Re: Chrome starts very slowly on Wayland

#48 2024-08-17 06:22:35

Re: Chrome starts very slowly on Wayland

#49 2024-08-17 06:30:48

Re: Chrome starts very slowly on Wayland

#50 2024-08-17 07:14:36

Re: Chrome starts very slowly on Wayland

Board footer