I have two manjaro laptops in daily use. Every 6-8 weeks, since late october / early november the system has frozen. It’s been the case on both pc’s. Nothing is working when this happens - no motion on the mouse, no reaction to keyboard indicator light when pressing caps-lock… The only thing to do is long press power button.
It has come to my attention that every time the problem has occurred has been at the moment a youtube video is near the end (still some seconds left) and I touch the touchpad in order to close the tab in firefox where the video is playing. It happens at the exact moment my finger makes contact with the touchpad, before any motion is initiated.
I’ve not been able to replicate the problem by restoring firefox session after reboot and play the same video again.
I thought for a while that the cause could be that I happened to touch the touchpad at the exact moment system was initiating session lock due to inactivity, but it also happens while presentation mode is enabled.
Any suggestions how to debug this?
Is this an invitation for speculation?
There are (or: should be) system logs (journalctl …) documenting what happened at the time.
Once or more than that inside this time frame?
Then it’s obviously not firefox
that’s at fault, nor the video that would be corrupt.
If it only happens every 6 to 8 weeks, then it’s most likely an intermittent hardware issue — possibly memory corruption due to electromagnetic interference.
marli
11 May 2025 18:16
4
I have not found any log entries with timestamp within a minute before/after freezing.
I don’t think hardware is the one to blame, as this behavior started at two very different laptops within two weeks. Nor can the kernel be blamed as one laptop was running 6.6 LTS, and still is running that kernel, while the other laptop has experienced the issue with every kernel from 6.9 to 6.12.
Both of these laptops are running for several weeks without reboot. Ever since this problem first occurred, they have not been rebooted other than when the freeze occurred. The cause could be firefox plugin could be failing when uptime becomes several weeks.
Could be - or not.
It’s hard to test when it happens so infrequently.
If you suspect some firefox extension - disable it (or all of them) …
Hardware issue is more likely - or cosmic rays messing with the RAM contents or the workings of the CPU …
some system information may help:
inxi -zv8
BG405
11 May 2025 22:05
6
6-8 weeks is rather good in terms of uptime when regularly watching YouTube videos. I assume you have plenty of RAM. Hopefully also some swap
.
Keep an eye on RAM and swap
usage:
watch -n60 free -h
I don’t think YouTube pre-loads the next video to any degree, but it might?
Once we see your inxi-zv8
output, it will help.
2 Likes
marli
14 May 2025 19:26
7
Sorry for the late reply. I spend a lot of time without internet coverage these days.
With 30GB of swap and 16GB of ram I don’t run out of ram while using firefox and a few text documents open in writer (which has been the case when the problem has occurred. I do use all of my ram when running VMs or do video editing. Hence my ram is “well tested”. It doesn’t make sence to blame hardware when the problem first showed up about the same time on two very different laptops.
Here’s the inxi output of the primary laptop: (This laptop has encrypted root, the other does not.)
# inxi -zv8
System:
Kernel: 6.12.19-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=ac75e81e-1a48-4c07-b3ae-4f42d4f70141 rw sysrq_always_enabled=1
apparmor=1 security=apparmor
cryptdevice=UUID=4dee491a-1bb6-413e-921e-7e4a7f8ccd25:luks-4dee491a-1bb6-413e-921e-7e4a7f8ccd25
root=/dev/mapper/luks-4dee491a-1bb6-413e-921e-7e4a7f8ccd25
resume=/dev/mapper/luks-b3cd44c0-994a-45ba-92f3-36d81d8c5f59
udev.log_priority=3 mem_sleep_default=deep
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: SCHENKER product: SCHENKER_VIA_14_SVI14E20 v: N/A
serial: <filter> Chassis: Notebook type: 10 serial: N/A
Mobo: SCHENKER model: L140CU serial: N/A part-nu: L140CU
uuid: 5844193a-3671-41e4-90e0-05b166f8188a UEFI: INSYDE v: 1.07.10
date: 09/06/2020
Battery:
ID-1: BAT0 charge: 53.3 Wh (100.0%) condition: 53.3/73.9 Wh (72.2%)
volts: 8.3 min: 7.7 model: Notebook BAT type: Li-ion serial: <filter>
status: full
Memory:
System RAM: total: 16 GiB available: 15.35 GiB used: 13.06 GiB (85.1%)
igpu: 32 MiB
Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
max-module-size: 16 GiB note: est.
Device-1: ChannelA-DIMM0 type: DDR4 detail: synchronous size: 8 GiB
speed: 2667 MT/s volts: curr: 1.2 min: 1.5 max: 1.5 width (bits): data: 64
total: 64 manufacturer: Samsung part-no: M471A1G44AB0-CTD serial: N/A
Device-2: ChannelB-DIMM0 type: DDR4 detail: synchronous size: 8 GiB
speed: 2667 MT/s volts: curr: 1.2 min: 1.5 max: 1.5 width (bits): data: 64
total: 64 manufacturer: Samsung part-no: M471A1K43CB1-CTD serial: <filter>
PCI Slots:
Slot: 1 type: PCIe status: available info: J_WLAN1 length: other volts: 3.3
bus-ID: 00:1d.1
Slot: 2 type: PCIe status: available info: J_SSD1 length: other volts: 3.3
bus-ID: 00:1d.4
CPU:
Info: model: Intel Core i5-10210U socket: BGA1528 (U3E1) note: check
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: 0xFC
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
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: 1501 min/max: 400/4200 base/boost: 1485/8300 scaling:
driver: intel_pstate governor: powersave volts: 0.7 V ext-clock: 100 MHz
cores: 1: 1501 2: 1501 3: 1501 4: 1501 5: 1501 6: 1501 7: 1501 8: 1501
bogomips: 33615
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
ibrs_enhanced ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx
monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq
pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand rdseed rdtscp
rep_good sdbg sep sgx smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3
stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx
vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
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: Enhanced / Automatic IBRS; IBPB:
conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW
loop
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: CLEVO/KAPOK
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: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:2 chip-ID: 04f2:b684
class-ID: 0e02 serial: <filter>
Display: x11 server: X.org v: 1.21.1.16 compositor: xfwm4 v: 4.20.0
driver: X: loaded: modesetting alternate: fbdev,vesa dri: iris gpu: i915
display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
Monitor-1: eDP-1 model: AU Optronics 0x623d built: 2018 res: 1920x1080
dpi: 158 gamma: 1.2 chroma: red: x: 0.639 y: 0.329 green: x: 0.298 y: 0.600
blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9b41 memory: 7.5 GiB unified: yes
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings x11: xprop
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
API: ALSA v: k6.12.19-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: brfjt state: up speed: -1 duplex: unknown mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-2: brlyc state: up speed: -1 duplex: unknown mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-3: brprt state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-4: dumfjt state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-5: dumlyc state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-6: dumprt state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-7: vboxnet0 state: down mac: <filter>
IF-ID-8: veth23490eth0 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-9: veth374813eth0 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-10: veth60442eth0 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-11: veth9603eth0 state: up speed: 10000 Mbps duplex: full
mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface 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:0a2b
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 48 state: down bt-service: N/A rfk-block:
hardware: no software: no address: see --recommends
Logical:
Message: No logical block device data found.
Device-1: luks-4dee491a-1bb6-413e-921e-7e4a7f8ccd25 maj-min: 254:0
type: LUKS dm: dm-0 size: 29.29 GiB
Components:
p-1: nvme0n1p2 maj-min: 259:2 size: 29.3 GiB
Device-2: luks-b3cd44c0-994a-45ba-92f3-36d81d8c5f59 maj-min: 254:1
type: LUKS dm: dm-1 size: 29.29 GiB
Components:
p-1: nvme0n1p3 maj-min: 259:3 size: 29.3 GiB
Device-3: luks-37c54d71-540e-4413-a464-d7be2de52505 maj-min: 254:2
type: LUKS dm: dm-2 size: 19.53 GiB
Components:
p-1: nvme0n1p4 maj-min: 259:4 size: 19.53 GiB
RAID:
Device-1: p type: zfs status: ONLINE level: linear raw: size: 872 GiB
free: 381 GiB allocated: 491 GiB zfs-fs: size: 909.74 GiB free: 353.66 GiB
Components: Online:
1: nvme0n1p5 maj-min: 259:5 size: 875.45 GiB
Drives:
Local Storage: total: raw: 953.87 GiB usable: 988.16 GiB
used: 582.3 GiB (58.9%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2200 MTFDHBA1T0TCK
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P1MU003 temp: 38.9 C
scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 29.29 GiB size: 28.67 GiB (97.86%) used: 16.29 GiB (56.8%)
fs: ext4 block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0
mapped: luks-4dee491a-1bb6-413e-921e-7e4a7f8ccd25 label: root
uuid: ac75e81e-1a48-4c07-b3ae-4f42d4f70141
ID-2: /boot/efi raw-size: 301 MiB size: 300.4 MiB (99.79%)
used: 448 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1 label: EFI uuid: CD7B-D52A
ID-3: /com/common raw-size: N/A size: 376.83 GiB used: 23.16 GiB (6.1%)
fs: zfs logical: p/common
ID-4: /com/iva raw-size: N/A size: 643.03 GiB used: 289.36 GiB (45.0%)
fs: zfs logical: p/iva
ID-5: /com/pr raw-size: N/A size: 359.9 GiB used: 6.24 GiB (1.7%) fs: zfs
logical: p/pr
ID-6: /com/vb raw-size: N/A size: 580.7 GiB used: 227.04 GiB (39.1%)
fs: zfs logical: p/vb
ID-7: /home raw-size: 19.53 GiB size: 19.05 GiB (97.57%)
used: 14.57 GiB (76.4%) fs: ext4 block-size: 4096 B dev: /dev/dm-2
maj-min: 254:2 mapped: luks-37c54d71-540e-4413-a464-d7be2de52505
label: home uuid: 56558bc2-bbc0-4835-b431-2a30c95f804e
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 29.29 GiB used: 5.65 GiB (19.3%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-b3cd44c0-994a-45ba-92f3-36d81d8c5f59 label: swap
uuid: 3d7b87d8-4e85-4ce7-ba3a-881aa819655b
Unmounted:
Message: No unmounted partitions found.
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-7:2 info: Chicony USB2.0 Camera type: video driver: uvcvideo
interfaces: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
power: 500mA chip-ID: 04f2:b684 class-ID: 0e02 serial: <filter>
Device-2: 1-10:3 info: Intel Bluetooth wireless interface type: bluetooth
driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 46.0 C pch: 42.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 1246 libs: 352 tools: pamac
pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
2: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
3: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
4: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
5: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
6: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
7: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
8: https://manjaro.kurdy.org/stable/$repo/$arch
9: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
10: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
11: https://manjaro.ynh.ovh/stable/$repo/$arch
12: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
13: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
14: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
15: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
16: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
17: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
18: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
19: https://mirror.zetup.net/manjaro/stable/$repo/$arch
20: https://muug.ca/mirror/manjaro/stable/$repo/$arch
21: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
22: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
23: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
24: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
25: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
26: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
27: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
28: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
29: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
30: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
31: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
32: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
33: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
34: https://mirror.hostiko.network/manjaro/stable/$repo/$arch
35: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
36: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
37: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
38: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
39: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
40: http://mirror.fcix.net/manjaro/stable/$repo/$arch
41: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
42: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
43: https://mirrors2.manjaro.org/stable/$repo/$arch
44: https://mirror.23m.com/manjaro/stable/$repo/$arch
45: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
46: https://mirror.easyname.at/manjaro/stable/$repo/$arch
47: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
48: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
49: https://mirror.init7.net/manjaro/stable/$repo/$arch
50: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
51: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
52: https://mirrors.manjaro.org/repo/stable/$repo/$arch
53: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
54: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
55: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
56: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
57: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
58: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
59: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
60: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
61: https://mirror.koddos.net/manjaro/stable/$repo/$arch
62: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
63: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
64: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
65: http://free.nchc.org.tw/manjaro/stable/$repo/$arch
66: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
67: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
68: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 458
1: cpu: 26.7% command: firefox pid: 764468 mem: 471.6 MiB (2.9%)
2: cpu: 9.9% command: firefox pid: 765191 mem: 73.4 MiB (0.4%)
3: cpu: 8.9% command: firefox pid: 764737 mem: 164.4 MiB (1.0%)
4: cpu: 7.5% command: firefox pid: 764800 mem: 220.7 MiB (1.4%)
5: cpu: 6.2% command: cinelerra-gg pid: 762384 mem: 493.5 MiB (3.1%)
Memory top: 5 of 458
1: mem: 4238.2 MiB (26.9%) command: VirtualBoxVM pid: 515958 cpu: 4.2%
2: mem: 493.5 MiB (3.1%) command: cinelerra-gg pid: 762384 cpu: 6.2%
3: mem: 471.6 MiB (2.9%) command: firefox pid: 764468 cpu: 26.7%
4: mem: 220.7 MiB (1.4%) command: firefox pid: 764800 cpu: 7.5%
5: mem: 178.7 MiB (1.1%) command: firefox pid: 1880 cpu: 3.6%
Info:
Processes: 458 Power: uptime: 10d 21h 42m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 47 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 6.12 GiB
services: upowerd,xfce4-power-manager Init: systemd v: 257
default: graphical tool: systemctl
Compilers: gcc: 14.2.1 Shell: Bash (su) v: 5.2.37
running-in: xfce4-terminal inxi: 3.3.37
BG405
14 May 2025 20:00
8
This is getting rather full and quite a bit of swap
is being consumed. I experience significant lag when my swap
has more than a few GB (even with an SSD!) and at about the level yours has, will start getting issues with the browser (Firefox in my case) misbehaving.
Periodic browser restarts will mitigate this, for a time, but eventually a full logout or reboot will be needed.
This is exactly why I suggested monitoring memory and swap usage; then you will be able to see when the problems start.
marli
15 May 2025 10:36
9
You consider 19% usage as full?
If you hibernate once, and you’ll see on resume that lots of the stuff you had in ram has been moved to swap. It will return to ram when needed. (compare free -h
before hibernate, after resume from hibernate, and after you have given all your open windows focus)
From your logic it sounds like you consider a reboot is required after every resume from hibernate. That doesn’t make sense to me.
BG405
15 May 2025 14:15
10
What I actually meant is that this amount of swap
in use during a running session will impact performance. When RAM is getting full and swap
is actively being used the amount of I/O needed to keep things running increases drastically, at least in my experience.
Usually, restarting the browser will clear some (but not necessarily, or indeed usually, all) the crud it accumulates due to memory leaks, etc.
The machine I primarily use as a media centre tends to get rebooted about every 3-4 weeks. This has half the RAM yours has (8G) and sees heavy use of YouTube.
I usually get away with several browser restarts before an actual reboot is needed, regardless of use of hibernate.
marli
15 May 2025 17:39
11
I’ve set an hourly date && free -h >> /var/log/swapusage.log
. We’ll see how it looks after the next freeze.
1 Like