Lag in form input in chrome

English Applications
1

hi

i use chrome under wayland and often when i type text in input text , that could take i few second before i see character.
i don’t have this issue with firefox.

i have a intel i3-10100 with 32 gig of ram

2

I’m not seeing that. Neither in Google’s rpm, nor in the flatpak. Which are you using?
Next: Is this on every website with input fields?
How many tabs are usually open?
GPU and drivers? Please show inxi -GSaz

3 
System:
  Kernel: 7.1.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.1.5-1-default
    root=UUID=63b88ee6-c1fd-44eb-8765-749c256d9988 splash=silent
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 6.7.3 tk: Qt v: N/A info: frameworks v: 6.28.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
    Tumbleweed 20260803
Graphics:
  Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: Lenovo
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:9bc8 class-ID: 0300
  Device-2: Logitech Brio 500
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 046d:0943
    class-ID: 0300 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev,intel dri: iris gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: AOC U3277WB serial: <filter> built: 2018 res:
    mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 140 gamma: 1.2
    size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 3840x2160 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.6 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CML GT2)
    device-ID: 8086:9bc8 memory: 30.35 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.357 layers: 1 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 630 (CML GT2) driver: mesa intel v: 26.1.6
    device-ID: 8086:9bc8 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 22.1.8 256 bits) driver: mesa llvmpipe v: 26.1.6 (LLVM 22.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

seem like more on facebook

4

First thing to try is to see if this problem exists in Plasma Wayland: Logout, in login screen left bottom select Plasma Wayland, login.

5

I would also be inclined to open the Chrome task manager and see what kind of CPU/memory utilization is happening during this. I have a few tabs that are slow and occasionally lock up, and often times this is caused by memory leaks (you can see if that’s a possibility by looking at memory utilization) or CPU utilization.

6

i already use wayland:

image
image604×612 49 KB

when i type in input text in facebook:

image
image3521×973 221 KB

7

Yea, I noticed in your “inxi -GSaz” output that you’re using wayland.

So, based on that, I suggest you do this:

  1. Logout of your current session.
  2. At the login screen (SDDM), at the bottom of screen, select “Plasma / X11”, then type password and login.

Now go test again at the website / etc that you’re having an issue … any different in response-time??

8

The usual X11 nonsense. Going back to X11 will fix nothing. Additionally the OP is using Plasma. This is the last Plasma version where X11 is supported…

1 Like