Posts: 29
Threads: 5
Joined: Sep 2018
Reputation:
1
Hi,
I'm also experiencing this issue. Like a few others on the thread, my setup is a Pi 3B+ with the official 7" DSI display and a Hifiberry AMP2. I boot the system from a USB flash drive (sandisk ultra fit 16BG).
Here's the initial log after boot:
Code: 20210411 145642 worker: -- Start
20210411 145642 worker: Successfully daemonized
20210411 145642 worker: Integrity check (passed)
20210411 145643 worker: File check (OK)
20210411 145644 worker: Session vacuumed
20210411 145644 worker: Session loaded
20210411 145644 worker: Debug logging (OFF)
20210411 145644 worker: -- Device
20210411 145644 worker: ALSA cards: (0:sndrpihifiberry | 1:empty | 2:empty | 3:empty
20210411 145644 worker: MPD config: (0:HiFiBerry Amp2 | mixer:(Digital) | card:0)
20210411 145644 worker: ALSA mixer actual (Digital)
20210411 145644 worker: ALSA Digital volume set to (0%)
20210411 145644 worker: -- System
20210411 145646 worker: Host (sunroom71)
20210411 145646 worker: moOde (7.1.0 2021-03-15)
20210411 145646 worker: RaspiOS (10.6)
20210411 145646 worker: Kernel (5.4.77-v7+ #1371)
20210411 145646 worker: Platform (Pi-3B+ 1.3 1GB)
20210411 145646 worker: ARM arch (armv7l, 32-bit kernel)
20210411 145646 worker: MPD ver (0.22.6_p0x3)
20210411 145646 worker: CPU gov (ondemand)
20210411 145646 worker: USB boot enabled
20210411 145646 worker: File system expanded
20210411 145646 worker: HDMI port off
20210411 145646 worker: -- Network
20210411 145646 worker: eth0 exists
20210411 145646 worker: eth0 address not assigned
20210411 145646 worker: wlan0 exists
20210411 145646 worker: Pi integrated wlan0 power save disabled
20210411 145646 worker: wifi country (UK)
20210411 145646 worker: wlan0 trying SSID (iris_5G)
20210411 145646 worker: IP addr (10.0.0.25)
20210411 145646 worker: Netmask (255.255.255.0)
20210411 145647 worker: Gateway (10.0.0.1)
20210411 145647 worker: Pri DNS (208.67.220.220)
20210411 145647 worker: Domain (208.67.222.222)
20210411 145647 worker: -- Audio
20210411 145647 worker: MPD conf updated
20210411 145647 worker: ALSA card number (0)
20210411 145647 worker: MPD audio output (HiFiBerry Amp2)
20210411 145647 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20210411 145647 worker: ALSA mixer name (Digital)
20210411 145647 worker: MPD volume control (hardware)
20210411 145647 worker: Hdwr volume controller exists
20210411 145647 worker: Max ALSA volume (100%)
20210411 145647 worker: Reset renderer active flags
20210411 145647 worker: CamillaDSP (off)
20210411 145647 worker: -- MPD
20210411 145647 worker: MPD started
20210411 145648 worker: MPD accepting connections
20210411 145648 worker: MPD output 1 ALSA Default (on)
20210411 145648 worker: MPD output 2 ALSA Crossfeed (off)
20210411 145648 worker: MPD output 3 ALSA Parametric EQ (off)
20210411 145648 worker: MPD output 4 ALSA Graphic EQ (off)
20210411 145648 worker: MPD output 5 ALSA Polarity Inv (off)
20210411 145648 worker: MPD output 6 ALSA CamillaDSP (off)
20210411 145648 worker: MPD output 7 ALSA Bluetooth (off)
20210411 145648 worker: MPD output 8 HTTP Server (off)
20210411 145648 worker: MPD crossfade (off)
20210411 145648 worker: MPD ignore CUE files (yes)
20210411 145648 worker: -- Feature availability
20210411 145648 worker: Source select (available)
20210411 145648 worker: Source select (source: MPD)
20210411 145648 worker: Source select (output: HiFiBerry Amp2)
20210411 145648 worker: Bluetooth (available)
20210411 145648 worker: Airplay renderer (available: started)
20210411 145648 worker: Spotify renderer (available: started)
20210411 145648 worker: Squeezelite (available)
20210411 145648 worker: RoonBridge renderer (not installed)
20210411 145648 worker: UPnP renderer (available)
20210411 145648 worker: DLNA server (available)
20210411 145648 worker: UPnP browser (available)
20210411 145648 worker: GPIO button handler (available)
20210411 145648 worker: Stream recorder (n/a)
20210411 145648 worker: -- Music sources
20210411 145648 worker: USB sources (none attached)
20210411 145649 worker: NAS and UPnP sources (mountall initiated)
20210411 145649 worker: -- Miscellaneous
20210411 145649 worker: USB volume knob (Off)
20210411 145649 worker: USB auto-mounter (udisks-glue)
20210411 145649 worker: LED0 (Off)
20210411 145649 worker: LED1 (Off)
20210411 145649 worker: Saved MPD vol level (0)
20210411 145649 worker: Preamp volume level (0)
20210411 145649 worker: MPD volume level (15) restored
20210411 145649 worker: ALSA Digital volume (53%)
20210411 145649 worker: Auto-play (Off)
20210411 145649 worker: LocalUI started
20210411 145649 worker: Maintenance interval (3 hrs)
20210411 145649 worker: Screen saver activation (Never)
20210411 145649 worker: Session permissions (OK)
20210411 145649 worker: Watchdog started
20210411 145649 worker: Ready
And here's the output from top when things have started to misbehave:
Code: top -b -n1 -1
top - 14:18:09 up 3:56, 1 user, load average: 0.52, 0.52, 0.48
Tasks: 152 total, 1 running, 151 sleeping, 0 stopped, 0 zombie
%Cpu0 : 10.5 us, 0.0 sy, 0.0 ni, 89.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu2 : 5.9 us, 11.8 sy, 0.0 ni, 82.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu3 : 15.0 us, 0.0 sy, 0.0 ni, 85.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 924.8 total, 21.2 free, 800.0 used, 103.6 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 44.4 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1025 pi 20 0 1047264 700628 48616 S 11.8 74.0 39:38.59 chromium-browse
20537 pi 20 0 10536 3096 2672 R 11.8 0.3 0:00.04 top
1016 pi 20 0 298548 36952 19844 S 5.9 3.9 6:45.11 chromium-browse
20239 root 20 0 0 0 0 I 5.9 0.0 0:15.11 kworker/2:1-events
1 root 20 0 15280 3892 2344 S 0.0 0.4 0:07.38 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.03 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kblockd
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
9 root 20 0 0 0 0 S 0.0 0.0 0:00.71 ksoftirqd/0
10 root 20 0 0 0 0 I 0.0 0.0 0:04.15 rcu_sched
11 root rt 0 0 0 0 S 0.0 0.0 0:00.05 migration/0
12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
14 root rt 0 0 0 0 S 0.0 0.0 0:00.06 migration/1
15 root 20 0 0 0 0 S 0.0 0.0 0:00.53 ksoftirqd/1
17 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-kblockd
18 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2
19 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/2
20 root 20 0 0 0 0 S 0.0 0.0 0:10.54 ksoftirqd/2
22 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/2:0H-kblockd
23 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3
24 root rt 0 0 0 0 S 0.0 0.0 0:00.05 migration/3
25 root 20 0 0 0 0 S 0.0 0.0 0:00.83 ksoftirqd/3
27 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/3:0H-kblockd
28 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
29 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
32 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kauditd
33 root 20 0 0 0 0 S 0.0 0.0 0:00.02 khungtaskd
34 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper
35 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 writeback
36 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0
54 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kblockd
55 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 blkcg_punt_bio
56 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdogd
58 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rpciod
60 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 xprtiod
61 root 20 0 0 0 0 S 0.0 0.0 0:01.31 kswapd0
62 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nfsiod
64 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 iscsi_eh
65 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 dwc_otg
66 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 DWC Notificatio
68 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 vchiq-slot/0
69 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 vchiq-recy/0
70 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 vchiq-sync/0
71 root 20 0 0 0 0 S 0.0 0.0 0:00.00 vchiq-keep/0
72 root 10 -10 0 0 0 S 0.0 0.0 0:00.00 SMIO
75 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
76 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 scsi_tmf_0
77 root 20 0 0 0 0 S 0.0 0.0 0:02.52 usb-storage
81 root -51 0 0 0 0 S 0.0 0.0 0:00.00 irq/166-usb-001
82 root 0 -20 0 0 0 I 0.0 0.0 0:00.10 kworker/1:1H-kblockd
83 root 20 0 0 0 0 S 0.0 0.0 0:00.68 jbd2/sda2-8
84 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 ext4-rsv-conver
85 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 ipv6_addrconf
87 root 0 -20 0 0 0 I 0.0 0.0 0:00.10 kworker/2:1H-kblockd
88 root 0 -20 0 0 0 I 0.0 0.0 0:00.13 kworker/0:1H-kblockd
90 root 0 -20 0 0 0 I 0.0 0.0 0:00.12 kworker/3:1H-kblockd
116 root 20 0 18976 3720 2868 S 0.0 0.4 0:00.64 systemd-journal
148 root 20 0 18628 2560 1648 S 0.0 0.3 0:01.33 systemd-udevd
167 root 10 -10 0 0 0 S 0.0 0.0 0:00.00 SMIO
187 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
190 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
192 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
193 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
222 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cfg80211
229 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 brcmf_wq/mmc1:0
231 root 20 0 0 0 0 S 0.0 0.0 0:05.33 brcmf_wdog/mmc1
233 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 uas
315 systemd+ 20 0 22984 3060 2352 S 0.0 0.3 0:00.48 systemd-timesyn
318 root 20 0 7712 4252 1188 S 0.0 0.4 0:02.85 haveged
322 _rpc 20 0 6576 2216 1892 S 0.0 0.2 0:00.07 rpcbind
358 root 39 19 3692 1584 1344 S 0.0 0.2 0:00.06 alsactl
360 message+ 20 0 7068 2932 2348 S 0.0 0.3 0:01.56 dbus-daemon
362 root 20 0 10740 2380 1972 S 0.0 0.3 0:00.15 wpa_supplicant
364 root 20 0 25860 2272 1924 S 0.0 0.2 0:00.12 rsyslogd
370 root 20 0 13388 3080 2412 S 0.0 0.3 0:00.60 systemd-logind
371 avahi 20 0 6244 2788 2364 S 0.0 0.3 0:04.25 avahi-daemon
379 root 20 0 27656 80 0 S 0.0 0.0 0:01.34 rngd
383 avahi 20 0 6120 288 0 S 0.0 0.0 0:00.00 avahi-daemon
411 root 20 0 11352 1968 1336 S 0.0 0.2 0:00.19 wpa_supplicant
473 root 20 0 2904 1376 968 S 0.0 0.1 0:00.06 dhcpcd
474 root 20 0 200928 7584 5204 S 0.0 0.8 0:01.32 php-fpm7.3
478 root 20 0 31980 4556 3144 S 0.0 0.5 0:00.97 nmbd
482 root 20 0 10928 2628 2060 S 0.0 0.3 0:00.03 sshd
486 root 20 0 10180 1844 1416 S 0.0 0.2 0:00.00 udisks-glue
489 root 20 0 29328 2588 1980 S 0.0 0.3 0:00.10 udisks-daemon
491 root 20 0 10644 684 308 S 0.0 0.1 0:00.00 udisks-daemon
494 root 20 0 38312 2816 2200 S 0.0 0.3 0:00.04 polkitd
499 root 20 0 50616 1168 0 S 0.0 0.1 0:00.00 nginx
500 www-data 20 0 51256 2808 1284 S 0.0 0.3 0:00.64 nginx
501 www-data 20 0 51116 2692 1284 S 0.0 0.3 0:00.03 nginx
502 www-data 20 0 50768 2208 888 S 0.0 0.2 0:00.00 nginx
503 www-data 20 0 50768 2208 888 S 0.0 0.2 0:00.00 nginx
505 www-data 20 0 201392 9776 6016 S 0.0 1.0 0:00.28 php-fpm7.3
509 root 20 0 40476 5376 3636 S 0.0 0.6 0:00.59 winbindd
510 root 20 0 201116 9360 4240 S 0.0 1.0 0:23.25 worker.php
514 root 20 0 4656 1396 1284 S 0.0 0.1 0:00.01 agetty
515 root 20 0 6964 1820 1704 S 0.0 0.2 0:00.01 agetty
544 root 20 0 40892 4332 2588 S 0.0 0.5 0:00.10 winbindd
550 root 20 0 48552 6388 4412 S 0.0 0.7 0:00.37 smbd
588 root 20 0 45424 3672 1796 S 0.0 0.4 0:00.01 smbd-notifyd
589 root 20 0 45424 2472 596 S 0.0 0.3 0:00.02 cleanupd
594 root 20 0 38932 3416 1744 S 0.0 0.4 0:00.02 winbindd
596 root 20 0 40476 4176 2456 S 0.0 0.4 0:00.04 winbindd
806 mpd 20 0 174432 10504 2760 S 0.0 1.1 0:01.19 mpd
823 root 20 0 10572 2424 2024 S 0.0 0.3 0:00.01 sudo
825 root 20 0 10572 2352 1952 S 0.0 0.2 0:00.00 sudo
828 root 20 0 131748 5636 2460 S 0.0 0.6 5:49.21 shairport-sync
829 root 20 0 24736 2588 2012 S 0.0 0.3 0:01.50 librespot
889 pi 20 0 3872 208 76 S 0.0 0.0 0:00.01 xinit
891 root 20 0 193752 17020 5308 S 0.0 1.8 0:01.08 Xorg
900 root 20 0 7676 1932 1764 S 0.0 0.2 0:12.73 watchdog.sh
918 pi 20 0 7676 2392 2248 S 0.0 0.3 0:00.00 .xinitrc
924 pi 20 0 579816 39940 17632 S 0.0 4.2 0:48.33 chromium-browse
939 pi 20 0 209120 11384 5660 S 0.0 1.2 0:00.24 chromium-browse
940 pi 20 0 209120 11352 5600 S 0.0 1.2 0:00.23 chromium-browse
942 pi 20 0 209120 7752 1992 S 0.0 0.8 0:00.00 chromium-browse
980 pi 20 0 280128 18824 10876 S 0.0 2.0 0:29.92 chromium-browse
990 pi 20 0 250512 13364 7292 S 0.0 1.4 0:00.29 chromium-browse
1018 pi 20 0 224308 8864 2244 S 0.0 0.9 0:00.00 chromium-browse
1040 www-data 20 0 201376 9636 6000 S 0.0 1.0 0:00.53 php-fpm7.3
1063 www-data 20 0 201376 9452 6004 S 0.0 1.0 0:00.17 php-fpm7.3
1250 www-data 20 0 201372 8952 5592 S 0.0 0.9 0:00.21 php-fpm7.3
1264 www-data 20 0 201372 8952 5596 S 0.0 0.9 0:00.17 php-fpm7.3
1645 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:2-xprtiod
1870 root 20 0 12440 3128 2316 S 0.0 0.3 0:00.18 sshd
1876 pi 20 0 14596 3244 2320 S 0.0 0.3 0:00.22 systemd
1878 pi 20 0 17024 1672 0 S 0.0 0.2 0:00.00 (sd-pam)
1921 pi 20 0 12440 2272 1452 S 0.0 0.2 0:03.01 sshd
1922 pi 20 0 8840 3832 2892 S 0.0 0.4 0:00.24 bash
15807 www-data 20 0 201372 8908 5552 S 0.0 0.9 0:00.08 php-fpm7.3
15814 www-data 20 0 201372 8344 5172 S 0.0 0.9 0:00.10 php-fpm7.3
17422 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:1
17801 root 20 0 0 0 0 I 0.0 0.0 0:00.36 kworker/1:1-events
18865 root 20 0 0 0 0 I 0.0 0.0 0:00.59 kworker/u8:2-events_unbound
19000 root 20 0 0 0 0 I 0.0 0.0 0:02.17 kworker/3:1-events_freezable
19218 root 20 0 0 0 0 I 0.0 0.0 0:42.71 kworker/2:0-events
19238 root 20 0 0 0 0 I 0.0 0.0 0:00.46 kworker/u8:1-events_unbound
19445 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0-mm_percpu_wq
19540 root 20 0 0 0 0 I 0.0 0.0 0:00.05 kworker/2:3-mm_percpu_wq
19597 root 20 0 0 0 0 I 0.0 0.0 0:00.85 kworker/0:1-events
19868 root 20 0 0 0 0 I 0.0 0.0 0:34.53 kworker/2:2-events_freezable_power_
20000 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/3:0-events_freezable
20013 root 20 0 0 0 0 I 0.0 0.0 0:00.20 kworker/u8:3-brcmf_wq/mmc1:0001:1
20164 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/0:2-events
20320 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/3:2-events_freezable
20354 root 20 0 0 0 0 I 0.0 0.0 0:00.11 kworker/u8:0-events_unbound
20479 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/1:2
20498 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0
20536 root 20 0 6456 360 308 S 0.0 0.0 0:00.00 sleep
I've no idea if these are red herrings, but I have set the display to sleep after 10 seconds, and wake on play. The pixel aspect ratio is set to square.
I'm more than happy to share other logs/settings info if that would be useful.
Cheers,
NB
Posts: 6,022
Threads: 176
Joined: Apr 2018
Reputation:
235
Sigh.
Even though the title of this thread clearly says "with HDMI" it seems to have mutated into an issue with DSI displays.
My official RPi 7" DSI touchscreen is encased with an RPi that drives an external USB DAC. With no release of moOde has this system experienced the reported local display failure mode. I've seen it occur only with HDMI displays.
What I find interesting about the me-too DSI posts to this thread is that Alaini93 is using a HiFiBerry DAC+ Pro while pgzh1, ciro73, and new_bloke are using a HiFiBerry AMP2 DAC. Is it just a coincidence that these few DSI failure reports involve I2S and the same driver or are we seeing real evidence here? [I'm beginning to feel like an epidemiologist here.]
I'm not going to pull my encased system apart to test with an I2S DAC.
Perhaps one of you four who report experiencing the failure using a DSI display could try switching to a different audio output---onboard audio jack or USB DAC---and seeing if the local display function continues to result in the chromium-browser eating up system memory.
Regards,
Kent
Posts: 29
Threads: 5
Joined: Sep 2018
Reputation:
1
(04-15-2021, 12:24 PM)TheOldPresbyope Wrote: Sigh.
Even though the title of this thread clearly says "with HDMI" it seems to have mutated into an issue with DSI displays.
My official RPi 7" DSI touchscreen is encased with an RPi that drives an external USB DAC. With no release of moOde has this system experienced the reported local display failure mode. I've seen it occur only with HDMI displays.
What I find interesting about the me-too DSI posts to this thread is that Alaini93 is using a HiFiBerry DAC+ Pro while pgzh1, ciro73, and new_bloke are using a HiFiBerry AMP2 DAC. Is it just a coincidence that these few DSI failure reports involve I2S and the same driver or are we seeing real evidence here? [I'm beginning to feel like an epidemiologist here.]
I'm not going to pull my encased system apart to test with an I2S DAC.
Perhaps one of you four who report experiencing the failure using a DSI display could try switching to a different audio output---onboard audio jack or USB DAC---and seeing if the local display function continues to result in the chromium-browser eating up system memory.
Regards,
Kent
I'm sorry that my post has irritated you. I'd be happy to delete it and start a new thread if you'd prefer. I test software for a living, and it's often the case that what looks like a specific scenario may have a root cause that manifests via other routes as well. I'd be more than happy to help investigate if it can be of use to the community of moode users. I have purchased a separate USB thumb drive for this purpose so I can switch between versions without a reinstall. Please let me know what information would be most useful in terms of output (other settings or logs).
Posts: 6,022
Threads: 176
Joined: Apr 2018
Reputation:
235
(04-15-2021, 03:08 PM)new_bloke Wrote: (04-15-2021, 12:24 PM)TheOldPresbyope Wrote: Sigh.
Even though the title of this thread clearly says "with HDMI" it seems to have mutated into an issue with DSI displays.
My official RPi 7" DSI touchscreen is encased with an RPi that drives an external USB DAC. With no release of moOde has this system experienced the reported local display failure mode. I've seen it occur only with HDMI displays.
What I find interesting about the me-too DSI posts to this thread is that Alaini93 is using a HiFiBerry DAC+ Pro while pgzh1, ciro73, and new_bloke are using a HiFiBerry AMP2 DAC. Is it just a coincidence that these few DSI failure reports involve I2S and the same driver or are we seeing real evidence here? [I'm beginning to feel like an epidemiologist here.]
I'm not going to pull my encased system apart to test with an I2S DAC.
Perhaps one of you four who report experiencing the failure using a DSI display could try switching to a different audio output---onboard audio jack or USB DAC---and seeing if the local display function continues to result in the chromium-browser eating up system memory.
Regards,
Kent
I'm sorry that my post has irritated you. I'd be happy to delete it and start a new thread if you'd prefer. I test software for a living, and it's often the case that what looks like a specific scenario may have a root cause that manifests via other routes as well. I'd be more than happy to help investigate if it can be of use to the community of moode users. I have purchased a separate USB thumb drive for this purpose so I can switch between versions without a reinstall. Please let me know what information would be most useful in terms of output (other settings or logs).
Re "irritation": Sorry, I was feeling more bemused than irritated. There may well be a root cause but posts should not get buried in pre-existing threads before it's known if there is a connection.
IMO its better to have multiple threads with specific titles that later get merged when more details are discovered. This makes it much easier for readers and testers to find relevant conversations. If you've tried the forum search feature you'll know what I mean.
Still, I'm a curmudgeon channeling my college librarian on this issue (her motto: a place for everything and everything in its place). This forum is as messily organized as most other forums are. It certainly beats the old days when all things "moOde" were posted to a single thread on the diyaudio.com forum.
Re: more info
1) I've seen no similar posts from users of DSI displays and DACs other than HiFiBerry Hats. If there are such folks having similar problems, we need to hear from them.
2) I've already suggested a test which could show whether the coincidence of HiFiBerry Hats/drivers is a red herring.
Other than that, for either display subsystem we need some way of understand what's driving the chromium-browser's render process to binge feed on system memory. The usual Linux logs and tools suffice to tell us which process it is but that's about it. So far, we haven't found a way to characterize this with enough supporting detail to make an intelligent case to the chromium devs and/or the Raspberry Pi OS devs (or even which group to approach).
All suggestions welcome.
Regards,
Kent
Posts: 29
Threads: 5
Joined: Sep 2018
Reputation:
1
Hi,
As suggested, I tried setting the audio output to the onboard jack - the same issue was observed as before:
Code: moodeutl -l
20210415 180640 worker: -- Start
20210415 180640 worker: Successfully daemonized
20210415 180640 worker: Integrity check (passed)
20210415 180641 worker: File check (OK)
20210415 180642 worker: Session vacuumed
20210415 180642 worker: Session loaded
20210415 180642 worker: Debug logging (OFF)
20210415 180642 worker: -- Device
20210415 180642 worker: ALSA cards: (0:Headphones | 1:empty | 2:empty | 3:empty
20210415 180642 worker: MPD config: (0:HiFiBerry Amp2 | mixer:(Digital) | card:0)
20210415 180642 worker: ALSA mixer actual (Headphone)
20210415 180642 worker: ALSA Headphone volume set to (0%)
20210415 180642 worker: -- System
20210415 180644 worker: Host (sunroom71)
20210415 180644 worker: moOde (7.1.0 2021-03-15)
20210415 180644 worker: RaspiOS (10.6)
20210415 180644 worker: Kernel (5.4.77-v7+ #1371)
20210415 180644 worker: Platform (Pi-3B+ 1.3 1GB)
20210415 180644 worker: ARM arch (armv7l, 32-bit kernel)
20210415 180644 worker: MPD ver (0.22.6_p0x3)
20210415 180644 worker: CPU gov (ondemand)
20210415 180644 worker: USB boot enabled
20210415 180644 worker: File system expanded
20210415 180644 worker: HDMI port off
20210415 180644 worker: -- Network
20210415 180644 worker: eth0 exists
20210415 180644 worker: eth0 address not assigned
20210415 180644 worker: wlan0 exists
20210415 180644 worker: Pi integrated wlan0 power save disabled
20210415 180644 worker: wifi country (UK)
20210415 180644 worker: wlan0 trying SSID (iris_5G)
20210415 180645 worker: IP addr (10.0.0.25)
20210415 180645 worker: Netmask (255.255.255.0)
20210415 180645 worker: Gateway (10.0.0.1)
20210415 180645 worker: Pri DNS (208.67.220.220)
20210415 180645 worker: Domain (208.67.222.222)
20210415 180645 worker: -- Audio
20210415 180645 worker: ALSA card number (0)
20210415 180645 worker: MPD audio output (Pi Headphone jack)
20210415 180645 worker: Audio formats (U8, S16_LE)
20210415 180645 worker: ALSA mixer name (Digital)
20210415 180645 worker: MPD volume control (hardware)
20210415 180645 worker: Hdwr volume controller not detected
20210415 180645 worker: Reset renderer active flags
20210415 180645 worker: CamillaDSP (off)
20210415 180645 worker: -- MPD
20210415 180645 worker: MPD started
20210415 180646 worker: MPD accepting connections
20210415 180646 worker: MPD output 1 ALSA Default (on)
20210415 180646 worker: MPD output 2 ALSA Crossfeed (off)
20210415 180646 worker: MPD output 3 ALSA Parametric EQ (off)
20210415 180646 worker: MPD output 4 ALSA Graphic EQ (off)
20210415 180646 worker: MPD output 5 ALSA Polarity Inv (off)
20210415 180646 worker: MPD output 6 ALSA CamillaDSP (off)
20210415 180646 worker: MPD output 7 ALSA Bluetooth (off)
20210415 180646 worker: MPD output 8 HTTP Server (off)
20210415 180646 worker: MPD crossfade (off)
20210415 180646 worker: MPD ignore CUE files (yes)
20210415 180646 worker: -- Feature availability
20210415 180646 worker: Source select (available)
20210415 180646 worker: Source select (source: MPD)
20210415 180646 worker: Source select (output: Pi Headphone jack)
20210415 180646 worker: Bluetooth (available)
20210415 180646 worker: Airplay renderer (available: started)
20210415 180646 worker: Spotify renderer (available: started)
20210415 180646 worker: Squeezelite (available)
20210415 180646 worker: RoonBridge renderer (not installed)
20210415 180646 worker: UPnP renderer (available)
20210415 180646 worker: DLNA server (available)
20210415 180646 worker: UPnP browser (available)
20210415 180646 worker: GPIO button handler (available)
20210415 180646 worker: Stream recorder (n/a)
20210415 180646 worker: -- Music sources
20210415 180646 worker: USB sources (none attached)
20210415 180647 worker: NAS and UPnP sources (mountall initiated)
20210415 180647 worker: -- Miscellaneous
20210415 180647 worker: USB volume knob (Off)
20210415 180647 worker: USB auto-mounter (udisks-glue)
20210415 180647 worker: LED0 (Off)
20210415 180647 worker: LED1 (Off)
20210415 180647 worker: Saved MPD vol level (0)
20210415 180647 worker: Preamp volume level (0)
20210415 180647 worker: MPD volume level (0) restored
20210415 180647 worker: ALSA volume level (None)
20210415 180647 worker: Auto-play (Off)
20210415 180647 worker: LocalUI started
20210415 180647 worker: Maintenance interval (3 hrs)
20210415 180647 worker: Screen saver activation (60)
20210415 180647 worker: Session permissions (OK)
20210415 180647 worker: Watchdog started
20210415 180647 worker: Ready
20210415 180744 coverart: mp3: /var/lib/mpd/music/NAS/Synology/Jukebox backup/Music/0smosis/Unknown Album/Hangin' with Lucie (1998).mp3
20210415 180744 coverart: mp3: Zend media exception: File does not contain ID3v2 tag
20210415 180813 worker: Job mpdcfg
Output from top:
Code: top -b -n1 -1
top - 20:37:12 up 2:30, 1 user, load average: 11.95, 10.09, 6.52
Tasks: 149 total, 2 running, 147 sleeping, 0 stopped, 0 zombie
%Cpu0 : 0.3 us, 8.3 sy, 0.0 ni, 0.0 id, 89.3 wa, 0.0 hi, 2.1 si, 0.0 st
%Cpu1 : 0.0 us, 10.2 sy, 0.0 ni, 0.0 id, 89.5 wa, 0.0 hi, 0.4 si, 0.0 st
%Cpu2 : 0.0 us, 5.4 sy, 0.0 ni, 92.7 id, 1.8 wa, 0.0 hi, 0.1 si, 0.0 st
%Cpu3 : 0.1 us, 9.8 sy, 0.0 ni, 0.0 id, 89.9 wa, 0.0 hi, 0.2 si, 0.0 st
MiB Mem : 924.8 total, 26.0 free, 852.7 used, 46.1 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 11.6 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
61 root 20 0 0 0 0 S 2.0 0.0 2:29.44 kswapd0
9793 root 20 0 0 0 0 I 1.7 0.0 0:28.98 kworker/2:3-events_freezable
1 root 20 0 15272 1952 400 D 0.8 0.2 0:10.33 systemd
77 root 20 0 0 0 0 R 0.7 0.0 1:30.74 usb-storage
886 pi 20 0 580840 22940 136 D 0.4 2.4 0:55.84 chromium-browse
9982 pi 20 0 10536 1396 932 R 0.4 0.1 0:00.20 top
82 root 0 -20 0 0 0 I 0.1 0.0 0:04.74 kworker/1:1H-kblockd
351 message+ 20 0 7068 580 0 S 0.1 0.1 0:01.35 dbus-daemon
942 pi 20 0 280128 8284 244 S 0.1 0.9 0:31.03 chromium-browse
979 pi 20 0 294476 21116 5140 S 0.1 2.2 4:33.41 chromium-browse
988 pi 20 0 1128172 711484 4428 D 0.1 75.1 22:54.35 chromium-browse
9985 root 20 0 6456 64 0 S 0.1 0.0 0:00.01 sleep
2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kblockd
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
9 root 20 0 0 0 0 S 0.0 0.0 0:02.95 ksoftirqd/0
10 root 20 0 0 0 0 I 0.0 0.0 0:03.11 rcu_sched
11 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/0
12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
14 root rt 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
15 root 20 0 0 0 0 S 0.0 0.0 0:02.98 ksoftirqd/1
17 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-kblockd
18 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2
19 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/2
20 root 20 0 0 0 0 S 0.0 0.0 0:07.41 ksoftirqd/2
22 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/2:0H-kblockd
23 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3
24 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/3
25 root 20 0 0 0 0 S 0.0 0.0 0:03.32 ksoftirqd/3
27 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/3:0H
28 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kdevtmpfs
29 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
32 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kauditd
33 root 20 0 0 0 0 S 0.0 0.0 0:00.01 khungtaskd
34 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper
35 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 writeback
36 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0
54 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kblockd
55 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 blkcg_punt_bio
56 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdogd
58 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rpciod
60 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 xprtiod
62 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nfsiod
64 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 iscsi_eh
65 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 dwc_otg
66 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 DWC Notificatio
68 root 1 -19 0 0 0 S 0.0 0.0 0:00.03 vchiq-slot/0
69 root 1 -19 0 0 0 S 0.0 0.0 0:00.00 vchiq-recy/0
70 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 vchiq-sync/0
71 root 20 0 0 0 0 S 0.0 0.0 0:00.00 vchiq-keep/0
72 root 10 -10 0 0 0 S 0.0 0.0 0:00.00 SMIO
75 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
76 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 scsi_tmf_0
81 root -51 0 0 0 0 S 0.0 0.0 0:00.00 irq/166-usb-001
83 root 20 0 0 0 0 S 0.0 0.0 0:00.42 jbd2/sda2-8
84 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 ext4-rsv-conver
85 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 ipv6_addrconf
87 root 0 -20 0 0 0 I 0.0 0.0 0:04.89 kworker/0:1H-kblockd
89 root 0 -20 0 0 0 I 0.0 0.0 0:02.62 kworker/2:1H-kblockd
102 root 0 -20 0 0 0 I 0.0 0.0 0:04.91 kworker/3:1H-kblockd
118 root 20 0 18976 1592 744 S 0.0 0.2 0:00.77 systemd-journal
146 root 20 0 18628 904 0 S 0.0 0.1 0:01.12 systemd-udevd
160 root 10 -10 0 0 0 S 0.0 0.0 0:00.00 SMIO
181 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
186 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
189 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
193 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mmal-vchiq
219 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 uas
225 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cfg80211
228 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 brcmf_wq/mmc1:0
231 root 20 0 0 0 0 S 0.0 0.0 0:02.64 brcmf_wdog/mmc1
309 _rpc 20 0 6576 328 0 S 0.0 0.0 0:00.07 rpcbind
312 root 20 0 7712 3092 28 S 0.0 0.3 0:04.83 haveged
313 systemd+ 20 0 22984 752 44 S 0.0 0.1 0:00.36 systemd-timesyn
353 root 39 19 3692 236 0 S 0.0 0.0 0:00.05 alsactl
356 root 20 0 13388 1736 1068 D 0.0 0.2 0:01.07 systemd-logind
360 root 20 0 25860 700 0 S 0.0 0.1 0:00.14 rsyslogd
362 avahi 20 0 6244 412 0 S 0.0 0.0 0:02.74 avahi-daemon
365 root 20 0 10740 408 0 S 0.0 0.0 0:00.23 wpa_supplicant
368 root 20 0 27656 140 0 S 0.0 0.0 0:03.16 rngd
376 avahi 20 0 6120 288 0 S 0.0 0.0 0:00.00 avahi-daemon
402 root 20 0 11352 636 0 S 0.0 0.1 0:00.35 wpa_supplicant
466 root 20 0 2904 408 0 S 0.0 0.0 0:00.08 dhcpcd
467 root 20 0 200928 4636 2256 S 0.0 0.5 0:02.78 php-fpm7.3
471 root 20 0 31980 1416 4 S 0.0 0.1 0:01.46 nmbd
475 root 20 0 10928 568 0 S 0.0 0.1 0:00.03 sshd
479 root 20 0 10180 476 48 S 0.0 0.1 0:00.01 udisks-glue
481 root 20 0 29368 664 0 S 0.0 0.1 0:00.11 udisks-daemon
484 root 20 0 10644 376 0 S 0.0 0.0 0:00.00 udisks-daemon
487 root 20 0 38312 660 40 S 0.0 0.1 0:00.05 polkitd
492 root 20 0 50616 1168 0 S 0.0 0.1 0:00.00 nginx
493 www-data 20 0 51164 1580 52 S 0.0 0.2 0:00.61 nginx
494 www-data 20 0 50768 1320 0 S 0.0 0.1 0:00.00 nginx
495 www-data 20 0 50768 1320 0 S 0.0 0.1 0:00.00 nginx
496 www-data 20 0 50768 1320 0 S 0.0 0.1 0:00.00 nginx
502 root 20 0 40476 2004 264 S 0.0 0.2 0:01.17 winbindd
503 root 20 0 201128 6592 1528 S 0.0 0.7 0:21.02 worker.php
507 root 20 0 4656 112 0 S 0.0 0.0 0:00.01 agetty
508 root 20 0 6964 116 0 S 0.0 0.0 0:00.01 agetty
533 root 20 0 40892 2024 280 S 0.0 0.2 0:00.43 winbindd
537 root 20 0 48552 2868 892 S 0.0 0.3 0:00.35 smbd
579 root 20 0 45424 1884 8 S 0.0 0.2 0:00.02 smbd-notifyd
580 root 20 0 45424 1876 0 S 0.0 0.2 0:00.02 cleanupd
583 root 20 0 38932 1672 0 S 0.0 0.2 0:00.08 winbindd
584 root 20 0 40476 2000 280 S 0.0 0.2 0:00.09 winbindd
792 root 20 0 10572 444 44 S 0.0 0.0 0:00.00 sudo
794 root 20 0 10572 444 44 S 0.0 0.0 0:00.01 sudo
797 root 20 0 122252 1092 0 S 0.0 0.1 1:00.21 shairport-sync
798 root 20 0 24736 596 0 S 0.0 0.1 0:01.78 librespot
824 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:1
851 pi 20 0 3872 132 0 S 0.0 0.0 0:00.01 xinit
852 root 20 0 193748 14480 2768 S 0.0 1.5 0:01.17 Xorg
862 root 20 0 7676 164 0 S 0.0 0.0 0:08.48 watchdog.sh
880 pi 20 0 7676 172 28 S 0.0 0.0 0:00.00 .xinitrc
901 pi 20 0 209120 5724 0 S 0.0 0.6 0:00.23 chromium-browse
902 pi 20 0 209120 5756 0 S 0.0 0.6 0:00.23 chromium-browse
904 pi 20 0 209120 5812 48 S 0.0 0.6 0:00.02 chromium-browse
952 pi 20 0 250512 6088 36 S 0.0 0.6 0:00.37 chromium-browse
981 pi 20 0 224308 6632 0 S 0.0 0.7 0:00.00 chromium-browse
1246 www-data 20 0 201376 5904 2544 S 0.0 0.6 0:00.13 php-fpm7.3
1286 www-data 20 0 201372 6000 2644 S 0.0 0.6 0:00.05 php-fpm7.3
1356 mpd 20 0 174440 11604 0 S 0.0 1.2 0:01.14 mpd
1416 www-data 20 0 201376 6404 2768 S 0.0 0.7 0:00.22 php-fpm7.3
1443 www-data 20 0 201376 6004 2644 S 0.0 0.6 0:00.07 php-fpm7.3
1450 www-data 20 0 201372 6184 2876 S 0.0 0.7 0:00.10 php-fpm7.3
1673 root 20 0 12440 860 48 S 0.0 0.1 0:00.20 sshd
1682 pi 20 0 14596 972 48 S 0.0 0.1 0:00.19 systemd
1683 pi 20 0 17016 1676 0 S 0.0 0.2 0:00.00 (sd-pam)
1724 pi 20 0 12440 840 12 S 0.0 0.1 0:02.68 sshd
1725 pi 20 0 8840 944 0 S 0.0 0.1 0:00.26 bash
1888 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:2
8355 root 20 0 0 0 0 I 0.0 0.0 0:01.79 kworker/3:2-events_freezable
8886 root 20 0 0 0 0 I 0.0 0.0 0:49.16 kworker/2:0-mm_percpu_wq
8952 root 20 0 0 0 0 I 0.0 0.0 1:23.73 kworker/2:2-events_freezable_power_
9564 root 20 0 0 0 0 I 0.0 0.0 0:00.64 kworker/u8:1-events_unbound
9633 root 20 0 0 0 0 I 0.0 0.0 0:00.13 kworker/1:2-events
9640 root 20 0 0 0 0 I 0.0 0.0 0:00.24 kworker/0:0-events
9808 root 20 0 0 0 0 I 0.0 0.0 0:00.37 kworker/0:1-events
9871 root 20 0 0 0 0 I 0.0 0.0 0:00.09 kworker/1:1-mm_percpu_wq
9901 root 20 0 0 0 0 I 0.0 0.0 0:00.26 kworker/u8:2-brcmf_wq/mmc1:0001:1
9919 root 20 0 0 0 0 I 0.0 0.0 0:00.35 kworker/3:0-events_freezable
9934 root 20 0 0 0 0 I 0.0 0.0 0:00.25 kworker/0:2-events
9936 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/2:1
9949 root 20 0 0 0 0 I 0.0 0.0 0:00.04 kworker/1:0-events
9971 root 20 0 0 0 0 I 0.0 0.0 0:00.07 kworker/3:1-events_freezable
9976 root 20 0 0 0 0 I 0.0 0.0 0:00.00 kworker/u8:0
Is there any mileage in attaching chrome dev tools to see what's going on? I found a couple of hints on how to do that, but would need to set an additional flag when the local display browser is started - can you point me in the direction of where that's done?
Posts: 6,022
Threads: 176
Joined: Apr 2018
Reputation:
235
OK, so the coincidence was a red herring. Not surprising, but a test is better than a guess.
As for running the local browser, have a look at /home/pi/.xinitrc
The last line launches the main chromium-browser process which spawns others.
Incidentally, /proc/<pid>/status contains lots of interesting info about a process. You can find the pid for the chromium-browser with ' type=renderer' by running ' ps aux|grep type=renderer'
Example:
Here the renderer process has pid=20035
Code: pi@710LD:~ $ ps aux|grep type=renderer
pi 20035 10.1 20.4 608876 193644 ? Sl Apr07 1368:53 /usr/lib/chromium-browser/chromium-browser-v7 --type=renderer --field-trial-handle=15160034476641370332,6248687004281252584,131072 --enable-features=OverlayScrollbar --lang=en-GB --enable-auto-reload --origin-trial-disabled-features=MeasureMemory --num-raster-threads=2 --enable-main-frame-before-activation --renderer-client-id=6 --no-v8-untrusted-code-mitigations --shared-files=v8_snapshot_data:100
pi@710LD:~ $ cat /proc/20035/status
Name: chromium-browse
Umask: 0022
State: S (sleeping)
Tgid: 20035
Ngid: 0
Pid: 20035
PPid: 19979
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 256
Groups: 4 20 24 27 29 44 46 60 100 105 109 997 998 999 1000
NStgid: 20035 4 1
NSpid: 20035 4 1
NSpgid: 19949 0 0
NSsid: 19906 0 0
VmPeak: 609960 kB
VmSize: 608876 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 324212 kB
VmRSS: 199268 kB
RssAnon: 44708 kB
RssFile: 83176 kB
RssShmem: 71384 kB
VmData: 172752 kB
VmStk: 132 kB
VmExe: 132528 kB
VmLib: 35304 kB
VmPTE: 782 kB
VmSwap: 0 kB
CoreDumping: 0
THP_enabled: 0
Threads: 11
SigQ: 0/6878
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001002
SigCgt: 00000001c0014a25
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
NoNewPrivs: 1
Seccomp: 2
Speculation_Store_Bypass: unknown
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 1
Mems_allowed_list: 0
voluntary_ctxt_switches: 52212316
nonvoluntary_ctxt_switches: 73246359
On my Linux desktop and laptops, the main chromium-browser process spawns many processes of type=renderer, more than a dozen even with just a single tab, but we're getting only one in moOde. I've never bothered to figure out why the difference.
Regards,
Kent
Posts: 39
Threads: 2
Joined: Apr 2018
Reputation:
2
Well, here is one of my experiences.
I use a Pi-3B, without any display, local mpd-library with approx. 1000 records and 8000 titles.
Whenever the usage of the input cache in the mdp settings is enabled and in the play-queue there are local titles i.e. titles that are in the mpd database, moode becomes unresponsive. I don't know whether this has something todo with the problem we are discussing here, but I thought it is worth checking the settings of mdp to see if it makes any change.
regards
Duke.G
1x RPi 3B, 1x RPi 4, 1x RPi 5, Moode 9; 6k flac Songs; 180k MP3 Songs; Asset-UpnP 186k Songs
The blues has got a hold of me, I believe I'm gettin' dizzy - ZZ Top
Posts: 6,022
Threads: 176
Joined: Apr 2018
Reputation:
235
(04-17-2021, 12:31 PM)duke.g Wrote: Well, here is one of my experiences.
I use a Pi-3B, without any display, local mpd-library with approx. 1000 records and 8000 titles.
Whenever the usage of the input cache in the mdp settings is enabled and in the play-queue there are local titles i.e. titles that are in the mpd database, moode becomes unresponsive. I don't know whether this has something todo with the problem we are discussing here, but I thought it is worth checking the settings of mdp to see if it makes any change.
regards
Duke.G
@ duke.g
Definitely a different issue which deserves its own thread where those with experience using the input cache feature can advise.
Regards,
Kent
Posts: 29
Threads: 5
Joined: Sep 2018
Reputation:
1
I have been able to successfully connect chrome dev tools to the instance running on the pi by adding the flag:
Code: --remote-debugging-port=9222
to the command in .xinitrc that launches the browser. I then opened an ssh tunnel to that port:
Code: ssh -L 9222:localhost:9222 user@host
I was then able to open the devtools on my local machine:
If this provides some useful information, I'd be happy to dig further, but I might need a bit of guidance as to where to look (nothing obvious leapt out so far.)
Cheers,
NB
Posts: 5
Threads: 1
Joined: May 2020
Reputation:
1
Hi
first time contributor to the forum, loving Moode since early 2020 .
I have a raspberry Pi 3B with an Hifiberry DAC + Pro and an Osoyoo 3.5" DSI touch screen and with Moode 7.1.0 installed
I verified a similar problem with Chromium memory usage increasing until freezing Moode completely. This started to happen since, at least, version 7.0.1 (although looking retrospectively I had previously several Chromium Aw! Snap Windows the could be from a similar problem). The problem occurs typically around 27 minutes after pausing the music player.
Trying to avoid being a "Me too!" I used the Local UI display with HDMI on , and with HDMI off while using the DSI display . Independently of the HDMI it always resulted in the system becoming completely frozen after some time.
Although not proficient in Linux , I think I found a work around to prevent the problem to occur. I edited the file .xinitrc and added at the end of the chromium-browser launch line:
--single-process --no-zygote --no-sandbox
It is now paused for more than 1 hour without any signs of increase in memory usage (with htop showing memory usage to vary between 236 and 259 Mb).
PS: I do not know why it works but I realized using top that the Chromium process that was using the memory had a "type=zygote" and tried to follow from there.
|
