Update Checker Using Massive Amount of RAM

Had a recent update to some Garuda configs garuda-fish-config in particular, and now the update checker is using massive amounts of RAM, got up to 13.3 GiB at one point, making my Sway system lag and freeze pretty badly… Makes my RAM usage peak up at 97-98%. Why is this using so much RAM…? It’ll jump up to 11.5 or more GiB of RAM usage for about 60 seconds, before starting to go back down again. In 5 minutes, it’ll do it again. Oh and it brings CPU usages to 98-99% as well.

garuda-inxi:

System:
  Kernel: 6.7.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=a9c12044-67cf-480c-890c-6ada1683400f rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: sway v: 0.3.2 info: waybar dm: greetd Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Dash F15 FX516PM_FX516PM
    v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: FX516PM v: 1.0 serial: <filter> UEFI: American
    Megatrends LLC. v: FX516PM.330 date: 05/15/2023
Battery:
  ID-1: BAT0 charge: 61.2 Wh (100.0%) condition: 61.2/76.0 Wh (80.6%)
    volts: 15.8 min: 15.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging cycles: 372
CPU:
  Info: model: 11th Gen Intel Core i7-11370H socket: U3E1 bits: 64
    type: MT MCP arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
    microcode: 0xB4
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1179 high: 3199 min/max: 400/4800 base/boost: 3300/4800
    scaling: driver: intel_pstate governor: powersave volts: 0.8 V
    ext-clock: 100 MHz cores: 1: 1271 2: 678 3: 400 4: 3199 5: 1410 6: 1679
    7: 400 8: 400 bogomips: 52838
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
    ports: active: DP-1 off: eDP-1 empty: DP-2,HDMI-A-1 bus-ID: 0000:00:02.0
    chip-ID: 8086:9a49 class-ID: 0300
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK
    driver: nouveau v: kernel non-free: 545.xx+ status: current (as of 2023-10;
    EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 ports: active: none empty: HDMI-A-2 bus-ID: 0000:01:00.0
    chip-ID: 10de:2520 class-ID: 0300
  Display: wayland server: Xwayland v: 23.2.4 compositor: sway v: 0.3.2
    driver: gpu: i915 display-ID: 1
  Monitor-1: DP-1 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2022 res: 2560x1440 dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43")
    diag: 801mm (31.5") ratio: 16:9 modes: max: 2560x1440 min: 640x480
  Monitor-2: eDP-1 model: Najing CEC Panda 0x004d built: 2019 res: 1920x1080
    dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: 1920x1080
  API: Vulkan Message: No Vulkan data available.
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
    bus-ID: 0000:00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:228e
    class-ID: 0403
  Device-3: Logitech G535 Wireless Gaming Headset
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:4 chip-ID: 046d:0ac4
    class-ID: 0a00
  API: ALSA v: k6.7.3-zen1-1-zen status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
    chip-ID: 8086:a0f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:2e:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:6 chip-ID: 8087:0026
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
  Local Storage: total: 1.38 TiB used: 23.74 GiB (1.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD BLACK SN770 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 731030WD temp: 35.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Samsung
    model: MZVLQ512HBLU-00B00 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: FXM7201Q temp: 31.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 146.5 GiB size: 146.5 GiB (100.00%)
    used: 23.74 GiB (16.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p7
    maj-min: 259:12
  ID-2: /boot/efi raw-size: 1.4 GiB size: 1.39 GiB (99.80%)
    used: 596 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p6
    maj-min: 259:11
  ID-3: /home raw-size: 146.5 GiB size: 146.5 GiB (100.00%)
    used: 23.74 GiB (16.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p7
    maj-min: 259:12
  ID-4: /var/log raw-size: 146.5 GiB size: 146.5 GiB (100.00%)
    used: 23.74 GiB (16.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p7
    maj-min: 259:12
  ID-5: /var/tmp raw-size: 146.5 GiB size: 146.5 GiB (100.00%)
    used: 23.74 GiB (16.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p7
    maj-min: 259:12
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.32 GiB used: 2.45 GiB (16.0%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 16.85 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:8
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2300
Info:
  Processes: 317 Uptime: 21m wakeups: 0 Memory: total: 16 GiB
  available: 15.32 GiB used: 2.79 GiB (18.2%) igpu: 64 MiB Init: systemd
  v: 255 default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1469 libs: 426 tools: pamac,paru Shell: garuda-inxi (sudo)
  default: Bash v: 5.2.26 running-in: foot inxi: 3.3.31
Garuda (2.6.23-1):
  System install date:     2024-02-01
  Last full system update: 2024-02-04
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Yes
  Failed units:            

No issues here, I just pulled down the most recent update and it goes back to nearly zero resource usage after the update is finished.

Did you change the update checker? This is the one we use in the ISO now:

It’s nice because it uses hardly any resources at all.

3 Likes

I didn’t change anything other than using garuda-update or clicking on the pacman updates widget to update. Other than that I haven’t touched pacman or any of it’s config files.

Oh I agree, love clicking to update or right-clicking to pacseek, great tool here. This only started occurring today after clicking the pacman-updates widget and updating first thing this morning. I even rebooted a few times to check if that was the issue.

As we can see when I did grep -i upgraded /var/log/pacman.log in the terminal, it shows the below updates from today:

[2024-02-04T05:01:31-0600] [ALPM] upgraded curl (8.6.0-1 -> 8.6.0-2)
[2024-02-04T05:01:31-0600] [ALPM] upgraded garuda-browser-settings (1.2.3-1 -> 1.2.4-1)
[2024-02-04T05:01:31-0600] [ALPM] upgraded garuda-common-settings (2.6.22-1 -> 2.6.23-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded garuda-fish-config (1.5.22-1 -> 1.5.23-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded imlib2 (1.12.1-2 -> 1.12.2-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded xdg-utils (1.2.0r28+g9b7d253-1 -> 1.2.0+1+gaf2fe0d-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded kguiaddons5 (5.113.0-1 -> 5.114.0-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded lib32-curl (8.6.0-1 -> 8.6.0-2)
[2024-02-04T05:01:32-0600] [ALPM] upgraded python-pip (23.3.2-1 -> 23.3.2-2)
[2024-02-04T05:01:32-0600] [ALPM] upgraded python-pydantic-core (1:2.14.6-1 -> 1:2.16.1-1)
[2024-02-04T05:01:32-0600] [ALPM] upgraded python-pydantic (2.5.3-1 -> 2.6.0-1)
[2024-02-04T05:01:56-0600] [ALPM] upgraded tela-circle-icon-theme-git (2023.10.07.r8.g559a16d2-1 -> 2023.10.07.r9.gc7939316-1)
[2024-02-04T05:01:56-0600] [ALPM] upgraded wolfssl (5.6.4-1 -> 5.6.6-1)
[2024-02-04T05:01:56-0600] [ALPM] upgraded vde2 (2.3.3-4 -> 2.3.3-5)

I can see where garuda-browser-settings, garuda-common-settings, and garuda-fish-config were upgraded. Just curious if whatever changes happened in any of the updates is what caused it.

Here are the rest of the updates since I installed Sway. Just goes back a couple days:

[2024-02-01T06:35:03-0600] [ALPM] upgraded garuda-update (4.4.1-1 -> 4.5.1-1)
[2024-02-01T06:36:01-0600] [ALPM] upgraded glibc (2.38-7 -> 2.38-8)
[2024-02-01T06:36:01-0600] [ALPM] upgraded libnghttp2 (1.59.0-1 -> 1.59.0-2)
[2024-02-01T06:36:02-0600] [ALPM] upgraded openssl (3.2.0-1 -> 3.2.1-1)
[2024-02-01T06:36:02-0600] [ALPM] upgraded gcc-libs (13.2.1-3 -> 13.2.1-4)
[2024-02-01T06:36:02-0600] [ALPM] upgraded curl (8.5.0-1 -> 8.6.0-1)
[2024-02-01T06:36:02-0600] [ALPM] upgraded binutils (2.41-3 -> 2.42-1)
[2024-02-01T06:36:02-0600] [ALPM] upgraded eza (0.17.3-1 -> 0.18.0-1)
[2024-02-01T06:36:02-0600] [ALPM] upgraded fakeroot (1.33-1 -> 1.33-2)
[2024-02-01T06:36:02-0600] [ALPM] upgraded gcc (13.2.1-3 -> 13.2.1-4)
[2024-02-01T06:36:02-0600] [ALPM] upgraded intel-media-driver (24.1.1-1 -> 24.1.2-1)
[2024-02-01T06:36:03-0600] [ALPM] upgraded lib32-glibc (2.38-7 -> 2.38-8)
[2024-02-01T06:36:03-0600] [ALPM] upgraded lib32-gcc-libs (13.2.1-3 -> 13.2.1-4)
[2024-02-01T06:36:03-0600] [ALPM] upgraded lib32-curl (8.5.0-1 -> 8.6.0-1)
[2024-02-01T06:36:03-0600] [ALPM] upgraded libpng (1.6.41-1 -> 1.6.42-1)
[2024-02-01T06:36:03-0600] [ALPM] upgraded lib32-libpng (1.6.41-1 -> 1.6.42-1)
[2024-02-01T06:36:03-0600] [ALPM] upgraded linux-zen (6.7.2.zen1-1 -> 6.7.2.zen1-2)
[2024-02-01T06:36:04-0600] [ALPM] upgraded linux-zen-headers (6.7.2.zen1-1 -> 6.7.2.zen1-2)
[2024-02-01T06:36:05-0600] [ALPM] upgraded noto-fonts (1:24.1.1-1 -> 1:24.2.1-1)
[2024-02-01T06:36:05-0600] [ALPM] upgraded sqlite (3.45.0-1 -> 3.45.1-1)
[2024-02-01T06:57:46-0600] [ALPM] upgraded lib32-openssl (1:3.2.0-1 -> 1:3.2.1-1)
[2024-02-01T08:29:33-0600] [ALPM] upgraded visual-studio-code-bin (1.85.2-1 -> 1.86.0-1)
[2024-02-01T09:10:32-0600] [ALPM] upgraded podman (4.9.0-1 -> 4.9.1-1)
[2024-02-01T09:10:32-0600] [ALPM] upgraded podman-docker (4.9.0-1 -> 4.9.1-1)
[2024-02-01T09:39:39-0600] [ALPM] upgraded linux-firmware-whence (20240115.9b6d0b08-1 -> 20240115.9b6d0b08-2)
[2024-02-01T09:39:39-0600] [ALPM] upgraded linux-firmware (20240115.9b6d0b08-1 -> 20240115.9b6d0b08-2)
[2024-02-01T10:45:15-0600] [ALPM] upgraded intel-ucode (20231114-1 -> 20231114-2)
[2024-02-02T00:11:06-0600] [ALPM] upgraded alsa-card-profiles (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded efivar (38-3 -> 39-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded libpipewire (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded libidn2 (2.3.4-3 -> 2.3.7-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded pipewire (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded mesa (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded gst-plugin-pipewire (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-libidn2 (2.3.4-2 -> 2.3.7-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-libpipewire (1:1.0.1-1 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-libva-mesa-driver (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-mesa (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-mesa-vdpau (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-pipewire (1:1.0.1-1 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded pipewire-audio (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded pipewire-jack (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-pipewire-jack (1:1.0.1-1 -> 1:1.0.2-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-vulkan-intel (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded vulkan-mesa-layers (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-vulkan-mesa-layers (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded vulkan-radeon (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:06-0600] [ALPM] upgraded lib32-vulkan-radeon (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded libreoffice-fresh (7.6.4-2 -> 24.2.0-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded libva-mesa-driver (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded licenses (20240115-1 -> 20240201-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded mesa-vdpau (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded pipewire-alsa (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded pipewire-pulse (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded pipewire-v4l2 (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded pipewire-x11-bell (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded pipewire-zeroconf (1:1.0.1-2 -> 1:1.0.2-1)
[2024-02-02T00:11:07-0600] [ALPM] upgraded python-trove-classifiers (2024.1.8-1 -> 2024.1.31-1)
[2024-02-02T00:11:08-0600] [ALPM] upgraded vulkan-intel (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T00:11:08-0600] [ALPM] upgraded vulkan-swrast (1:23.3.4-2 -> 1:23.3.5-1)
[2024-02-02T07:51:17-0600] [ALPM] upgraded qt5-base (5.15.12+kde+r149-1 -> 5.15.12+kde+r150-1)
[2024-02-02T08:29:25-0600] [ALPM] upgraded linux-zen (6.7.2.zen1-2 -> 6.7.3.zen1-1)
[2024-02-02T08:29:26-0600] [ALPM] upgraded linux-zen-headers (6.7.2.zen1-2 -> 6.7.3.zen1-1)
[2024-02-02T10:10:52-0600] [ALPM] upgraded brave-beta-bin (1.63.141-1 -> 1.63.142-1)
[2024-02-02T10:10:52-0600] [ALPM] upgraded linux-lts (6.6.14-2 -> 6.6.15-1)
[2024-02-02T10:10:53-0600] [ALPM] upgraded linux-lts-headers (6.6.14-2 -> 6.6.15-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded alsa-card-profiles (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded libpipewire (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded gst-plugin-pipewire (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded lib32-libpipewire (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded lib32-pipewire (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-audio (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-jack (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded lib32-pipewire-jack (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-alsa (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-pulse (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-v4l2 (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-x11-bell (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T10:38:42-0600] [ALPM] upgraded pipewire-zeroconf (1:1.0.2-1 -> 1:1.0.3-1)
[2024-02-02T12:21:06-0600] [ALPM] upgraded kanshi (1.5.0-1 -> 1.5.1-1)
[2024-02-02T12:21:06-0600] [ALPM] upgraded swayimg (2.0-2 -> 2.1-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded tzdata (2023d-1 -> 2024a-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded floorp (11.8.2-2 -> 11.9.0-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded fzf (0.45.0-1 -> 0.46.1-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded lzip (1.23-2 -> 1.24-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded neon (0.32.5-2 -> 0.33.0-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded podman (4.9.1-1 -> 4.9.2-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded podman-docker (4.9.1-1 -> 4.9.2-1)
[2024-02-03T11:08:46-0600] [ALPM] upgraded swayimg (2.1-1 -> 2.1-2)

I can’t explain very well, so. :grin:
Just some gitlab changes.

2 Likes

No worries. :slight_smile:
So I’m wondering if the issue is with waybar-module-pacman-updates package then if nothing crazy was changed with the Garuda packages. It’s definitely an odd issue I haven’t encountered before.

Part of the package changes can be found here:

In case of such commit messages chore(packages): update packages [skip ci] you can check the corresponding settings repo for what exactly changed. This means a new tag got pushed in a settings repo. There were changelogs attached to those commits at one point, though after refactoring the pipeline there was no easy way to get the changelog. Will have to add this back in a different way.

2 Likes

Thanks, I’ll save this so I can keep an eye on changes in the future.

1 Like

Someone else had a similar-sounding issue with this package last week:

I guess it kind of went away on its own so they closed the issue. :thinking:

If you are able to reproduce the issue or collect some data points, I would encourage you to chime in on that thread and see if you can help figure out what is happening to you guys.


Edit to add a follow-up thought:

@jpierce.coder I just saw your comment in this other thread:

It occurred to me it seems possible these two issues could be related. If the checkupdates utility is repeatedly attempting to connect to repository mirrors that are currently having connectivity issues, it may lead to timeouts and resource consumption as the utility waits for responses.

I don’t know this for sure (just kind of thinking out loud here), but it could be that the Waybar utility is continuing to kick off additional instances of checkupdates while the old ones hang due to the mirror issue. Eventually all the hung checkupdates processes could start to pile up. That would explain the resource usage climbing out of control.


Edit 2

I ended up chiming in on this issue to see what the developer thinks about this theory, and if they would be willing to amend the code so only a single sync_database process will run at a given time (so they can’t pile up if they get hung on a mirror issue). https://github.com/coffebar/waybar-module-pacman-updates/issues/4#issuecomment-1925863817

2 Likes

I think this is a really good and valid theory, and makes sense from a logic POV as to why this could be happening. I’m on GH so I’ll follow that thread if possible and see what he comes back with. It happens sporadically so if a mirror intermittently goes on and offline, that could happen for sure. I commented on that thread so we’ll see what he says. It’s not having an issue right now and a temporary fix for me is to use update remote fix. Hopefully he can get it fixed soon.

Wow, he already fixed it! :star_struck:

4 Likes

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