Syncthing causing high CPU in gnome-shell?

Running syncthing seems to cause high cpu usage in gnome-shell for some reason for about the last week or so and I'm not sure what to do about it other than not run syncthing. It might have been happening longer than that, but I only became aware of with the system being sluggish since the gnome update.

syncthing off:
gnome shell tends to be less than 15% of cpu core on average.

Syncthing on:
gnome shell tends to be between 30%-50% of cpu core on average.

running "journalctl /usr/bin/gnome-shell --since today":

"Nov 13 18:23:49 ROGGAR gnome-shell[5285]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x55589fe038b0] in animation of duration 200ms but not on stage.
Nov 13 18:23:50 ROGGAR gnome-shell[5285]: Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path โ€œ/org/gnome/Terminal/Searc>
Nov 13 18:24:23 ROGGAR gnome-shell[5285]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7600036
Nov 13 18:27:02 ROGGAR gnome-shell[5285]: JS ERROR: TypeError: this.actor is null
                                          [email protected]:///org/gnome/shell/ui/windowManager.js:138:25
                                          [email protected]:///org/gnome/shell/ui/windowManager.js:150:35
                                          _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22
                                          _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60
                                          [email protected]:///org/gnome/shell/ui/windowManager.js:1596:21
                                          [email protected]:///org/gnome/shell/ui/windowManager.js:1564:39
                                          _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22
                                          _easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64
Nov 13 18:32:46 ROGGAR gnome-shell[5285]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e00004
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:35:58 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:36:38 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)
Nov 13 18:37:08 ROGGAR gnome-shell[5285]: (../libsoup/libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)"
garuda-inxi:
System:
  Kernel: 6.0.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=7e213ff5-2bfe-4fc8-a7e4-355d44341375 rw [email protected]
    quiet
    cryptdevice=UUID=b7fc4c17-2b1b-43b0-af83-fff7d215f624:luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624
    root=/dev/mapper/luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624 quiet splash
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=/dev/mapper/luks-8f173e6c-08d2-4f4b-a9b3-461262a8d70d
    systemd.unified_cgroup_hierarchy=0 loglevel=3
  Desktop: GNOME v: 43.1 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 43.0
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: Zephyrus G GU502DU_GA502DU v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: GU502DU v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: GU502DU.306 date: 03/10/2021
Battery:
  ID-1: BAT0 charge: 61.4 Wh (100.0%) condition: 61.4/76.0 Wh (80.9%)
    volts: 15.8 min: 15.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging
CPU:
  Info: model: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx bits: 64
    type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
    built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
    stepping: 1 microcode: 0x8108102
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
    desc: 1x4 MiB
  Speed (MHz): avg: 2700 high: 2944 min/max: 1400/2300 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 2943 2: 2300
    3: 2300 4: 2942 5: 2300 6: 2944 7: 2933 8: 2940 bogomips: 36725
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: ASUSTeK
    driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 520.xx+
    status: current (as of 2022-10) arch: Turing code: TUxxx
    process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:2191 class-ID: 0300
  Device-2: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 06:00.0 chip-ID: 1002:15d8
    class-ID: 0300 temp: 57.0 C
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
    compositor: gnome-shell driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau,radeon alternate: fbdev,nv,vesa
    dri: radeonsi gpu: amdgpu display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: Najing CEC Panda 0x002d built: 2018
    res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon Vega 10 Graphics
    (raven LLVM 14.0.6 DRM 3.48 6.0.8-zen1-1-zen) direct render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:1aeb class-ID: 0403
  Device-2: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 06:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 06:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound API: ALSA v: k6.0.8-zen1-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    vendor: AzureWave driver: rtw_8821ce v: N/A modules: rtw88_8821ce pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
    chip-ID: 10ec:c821 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: c000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 5-2:3 chip-ID: 13d3:3530 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 686.82 GiB (48.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston
    model: RBUSNS8154P3512GJ3 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
    rev: E8FK11.T temp: 39.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Crucial model: CT1000P5SSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: P4CR311 temp: 50.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 905.73 GiB size: 905.73 GiB (100.00%)
    used: 686.82 GiB (75.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 756 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:6
  ID-3: /home raw-size: 905.73 GiB size: 905.73 GiB (100.00%)
    used: 686.82 GiB (75.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624
  ID-4: /var/log raw-size: 905.73 GiB size: 905.73 GiB (100.00%)
    used: 686.82 GiB (75.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624
  ID-5: /var/tmp raw-size: 905.73 GiB size: 905.73 GiB (100.00%)
    used: 686.82 GiB (75.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-b7fc4c17-2b1b-43b0-af83-fff7d215f624
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 23.16 GiB used: 2.2 MiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 25.48 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-8f173e6c-08d2-4f4b-a9b3-461262a8d70d
Sensors:
  System Temperatures: cpu: 57.2 C mobo: N/A gpu: amdgpu temp: 57.0 C
  Fan Speeds (RPM): cpu: 3900
Info:
  Processes: 400 Uptime: 21h 3m wakeups: 8 Memory: 23.16 GiB
  used: 7.3 GiB (31.5%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2084
  pm: pacman pkgs: 2021 libs: 530 tools: pamac,paru pm: flatpak pkgs: 63
  Shell: fish v: 3.5.1 running-in: gnome-terminal inxi: 3.3.23
Garuda (2.6.9-1):
  System install date:     2022-06-30
  Last full system update: 2022-11-12
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:            grub-btrfs-snapper.service systemd-oomd.socket

Syncthing can use a lot of CPU if the files you have asked it to sync are changing, or it is in the process of catching up with a change, because it hashes all the files. What files do you have Syncthing monitoring?

The error messages you posted do not implicate Syncthing in any way as far as I can tell (I don't think Syncthing uses libsoup, hopefully someone will correct me if I am wrong), although obviously Syncthing does not log errors to /usr/bin/gnome-shell in the first place.

Most Syncthing setups log to stdout, but you can set up a persistent log if you want to keep an eye on it by running syncthing -logfile /path/to/logfile. It can't hurt to keep an eye on it and look for any error messages or similar.

This person appears to be getting the same error message, although this issue hasn't seen any action yet.

The first thing I would try would be to disable all your GNOME Shell extensions and see if you observe any different behavior. If taking down all extensions resolves the issue, try bringing them back one at a time to single out the bad apple.

3 Likes

Yea, I'm not sure why there is a correlation either..
I tried turning off extensions, which is how I figured out Syncthing was related somehow..
When I stop the syncthing service from the syncthing-gtk gnome extension, CPU usage goes back to normal. The logging events for Syncthing all seem normal as far as I can tell. The libsoup events only seem to happen when the syncthing user-service is running. When I stop the service, Gnome-shell goes back to normal cpu even with all my extensions on. Then I tried starting/stopping the service from the terminal with the extension disabled to see if it made a difference and I still get the same results.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.