Increasing ram usage seconds after log in

Hello,

I'm having severe ram issues and I havent seen any posts than can help. A few minutes after logging in my pc suddenly started crashing. I noticed the ram started getting used up (I have 16gb) in a matter of seconds, but no apps (that I could see) in the system were taking that ram up, it just kept increasing until it crashed. I would greatly appreciate help, as I can only use my laptop in less than 10 minutes at a time. I used garuda-inxi twice in the span of 3 minutes and as you can see in the processes, the ram usage eventually reached 100%

Kernel: 6.3.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@_backup_20230202132317539/boot/vmlinuz-linux-zen
root=UUID=b2280a70-5db8-4b3f-8f5f-11686a66ea07 rw
rootflags=subvol=@_backup_20230202132317539 quiet quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: HP product: HP ProBook 440 G7 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: HP model: 869D v: KBC Version 02.2A.00 serial: <superuser required>
UEFI: HP v: S71 Ver. 01.05.04 date: 05/11/2020
Battery:
ID-1: BAT0 charge: 33.1 Wh (79.8%) condition: 41.5/41.5 Wh (100.0%)
volts: 11.4 min: 11.6 model: Hewlett-Packard Primary type: Li-ion
serial: <filter> status: discharging
CPU:
Info: model: Intel Core i5-10210U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check gen: core 10 level: v3 note: check
built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1846 high: 1957 min/max: 400/4200 scaling:
driver: intel_pstate governor: performance cores: 1: 1900 2: 1957 3: 1700
4: 1880 5: 1880 6: 1900 7: 1796 8: 1761 bogomips: 33599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:9b41 class-ID: 0300
Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard
driver: nvidia v: 535.54.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1d13
class-ID: 0302
Device-3: Quanta HP HD Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:2 chip-ID: 0408:5373
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
alternate: fbdev,intel,nv,vesa dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: BOE Display 0x0827 built: 2018 res: 1366x768
hz: 60 dpi: 112 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14")
ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 23.1.3 renderer: Mesa Intel UHD Graphics (CML GT2)
direct-render: Yes
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: Hewlett-Packard
driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0401
API: ALSA v: k6.3.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 0.3.71 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 Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:02f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down 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: 1-10:3 chip-ID: 8087:0026
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 121.4 GiB (26.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD050V
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1Q scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.47 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C pch: 36.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 288 Uptime: 3m wakeups: 1 Memory: available: 15.47 GiB
used: 8.04 GiB (51.9%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 2091
libs: 585 tools: gnome-software,octopi,paru Shell: fish v: 3.6.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
head: cannot open '/var/log/pacman.log' for reading: No such file or directory
System install date:
Last full system update: 2023-06-27
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:            nmb.service
System:
Kernel: 6.3.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@_backup_20230202132317539/boot/vmlinuz-linux-zen
root=UUID=b2280a70-5db8-4b3f-8f5f-11686a66ea07 rw
rootflags=subvol=@_backup_20230202132317539 quiet quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: HP product: HP ProBook 440 G7 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: HP model: 869D v: KBC Version 02.2A.00 serial: <superuser required>
UEFI: HP v: S71 Ver. 01.05.04 date: 05/11/2020
Battery:
ID-1: BAT0 charge: 32.8 Wh (79.0%) condition: 41.5/41.5 Wh (100.0%)
volts: 11.4 min: 11.6 model: Hewlett-Packard Primary type: Li-ion
serial: <filter> status: discharging
CPU:
Info: model: Intel Core i5-10210U bits: 64 type: MT MCP
arch: Comet/Whiskey Lake note: check gen: core 10 level: v3 note: check
built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1639 high: 1669 min/max: 400/4200 scaling:
driver: intel_pstate governor: performance cores: 1: 1609 2: 1662 3: 1624
4: 1669 5: 1610 6: 1669 7: 1607 8: 1669 bogomips: 33599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:9b41 class-ID: 0300
Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard
driver: nvidia v: 535.54.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1d13
class-ID: 0302
Device-3: Quanta HP HD Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:2 chip-ID: 0408:5373
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
alternate: fbdev,intel,nv,vesa dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: BOE Display 0x0827 built: 2018 res: 1366x768
hz: 60 dpi: 112 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14")
ratio: 16:9 modes: 1366x768
API: OpenGL v: 4.6 Mesa 23.1.3 renderer: Mesa Intel UHD Graphics (CML GT2)
direct-render: Yes
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: Hewlett-Packard
driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0401
API: ALSA v: k6.3.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 0.3.71 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 Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:02f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down 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: 1-10:3 chip-ID: 8087:0026
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 121.4 GiB (26.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD050V
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1Q scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 121.39 GiB (26.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.47 GiB used: 1.81 GiB (11.7%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.0 C pch: 40.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 285 Uptime: 5m wakeups: 1 Memory: available: 15.47 GiB
used: 15.05 GiB (97.2%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 2091
libs: 585 tools: gnome-software,octopi,paru Shell: fish v: 3.6.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
head: cannot open '/var/log/pacman.log' for reading: No such file or directory
System install date:
Last full system update: 2023-06-27
Is partially upgraded:   No

Thanks in advance

Looks like your are booted to an old backup image. I am assuming you are trying to find a backup that was before this problem?
Try restoring a working snapshot/backup (if there is one), rebooting, and then do a garuda-update to see if the issue persists.
(There has been a lot of recent kernel work that a more recent version could be your fix even.)

2 Likes

Yeah I loaded up an older one as I accidentally caused a partial update, and couldn’t even access my application manager, and couldn’t do a system update. I just tried the latest snapshot that showed up, but those issues were still present (the one I currently been using doesn’t have these issues and I was able to do a system update, the ram issue only recently started occuring

I'll try a system update anyways, but I have poor reception so it might take a while
Edit: It's not possible, the update is too big and by that point my pc would crash. I tried garuda-update, put my pc crashed before it could finish

Something you could try would be running htop or similar immediately after booting, so that you could see which processes are taking most of your RAM.
Another thing you could try is chrooting from your live USB and, if RAM usage is normal there, try garuda-update inside chroot.

3 Likes

Booting into a snapshot is not enough, you need to restore the snapshot, so your actual system becomes the snapshot, then reboot to your actual system. Even if you manage to solve the problem, if you do it from within a snapshot it won’t fix anything.

I think this is good advice. The application running off with your memory will probably be easy to identify in htop. Then, just kill that process and see if your system is stable enough to take an update.

3 Likes

I found two both taking 49.6% mem respectively, and both in usr/lib/packagekitd. I tried killing them with no avail.
Along with that around 16,000 different PID (sorry I’m not sure what it stands for), all taking around 0.1%.
I’ll try rebooting the snapshot as a last resort, because most applications wouldn’t even function, so I’m not sure I could fix the partial update issue

Using PackageKit on an Arch-based system is not recommended, see here: pacman/Tips and tricks - ArchWiki

You should use Pacman for package management whenever possible, not Discover or other PackageKit front ends.

This is not enough information. What did you try? What was the outcome?

Try this:

sudo killall packagekitd

Then update the system.

garuda-update
3 Likes

This stopped the ram from increasing, so I’ll update my system and see if the issue still persist, thank you.
Edit: It only works for a few minutes, so I have to keep killing it every few minutes, it’s still manageable enough to let me update my system

Is there a specific reason why you are willing to put up with this software and not just remove it?

Honestly I’m just not sure if it’s safe to. It’s causing problems but I don’t want to make it an even bigger mess. I didn’t manually install it, so I’m not sure where it came from or what it does/if it has dependencies

Well your system is pretty much already unusable as it is. As you said you have to constantly kill it to keep your system working. In the long run you would still have only two options either remove this software or reinstall your OS. I don't think keeping an eye on your system resources all the time you are using it is quite feasible.

2 Likes

You’re right, but now I’m not sure how to remove it either. I tried pacman -Qe, but the only package similar to packagekitd is packagekit-qt5
Looking for through the file explorer i can’t seem to find packagekitd either

use

pacman -Qs packagekit

that should return all the packages in your system with the name packagekit in it unlike your earlier command that restricted output to explicitly installed packages. However, if I am not wrong the package you are looking for is called gnome-packagekit. Though you can always confirm that with the above command. If I am right then,

sudo pacman -Rns gnome-packagekit

should do the job of removing it. Oh, also

sudo paccache -ruk0

To clean pacman cache of uninstalled packages.

Edit; Just wanna add if you are already running garuda-update in the background then I suggest you wait for it to finish before you remove gnome-packagekit so that you don't end up causing db lock conflicts.

2 Likes

These are the packages i found

local/apper 1.0.0-5
An application and package manager using PackageKit
local/gnome-software-packagekit-plugin 42.4-1
PackageKit support plugin for GNOME Software
local/libpackagekit-glib 1.2.6-2
GLib library for accessing PackageKit
local/packagekit 1.2.6-2
A system designed to make installation and updates of packages easier
local/packagekit-qt5 1.1.1-1
Qt5 bindings for PackageKit

I’m not sure if it’s one of these, either way i tried

sudo pacman -Rns gnome-packagekit

no packages were found though

error: target not found: gnome-packagekit

Yeah bcoz gnome-packagekit doesn't exist on your system. But those other softwares that you see on your screen they need to go.

sudo pacman -Rns packagekit apper gnome-software-packagekit-plugin libpackagekit-glib packagekit-at5

following this use

cleanup

command this is an alias to sudo pacman -Rns (pacman -Qtdq) which will remove all orphan packages in your system.

3 Likes

Just a little explaining.

I hope you don't misunderstand that you always need to remove All software listed by pacman -Qs command. This was a special case since packagekit itself contained the packagekitd service and the other packages were dependant on packagekit to work hence they too had to go. This is not always the case.

1 Like

Yeah I understand, thanks for clarifying though, and thanks so much for the help

1 Like

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