You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2021-01-09 03:30:07
- Ratcatcher
- Member
- Registered: 2021-01-09
- Posts: 4
xfce4-color-set | software or hardware problem?
It started when my computer to freeze every few days. I don't know very well what to do in this case, but I found something in the logs:
journalctl -x -p3 -b1
System:
Kernel: 5.4.85-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64
root=UUID=429c9339-251d-4584-80f0-d28d1d27c1cb rw quiet
resume=UUID=142716b6-7936-411c-b296-daaff078460f udev.log_priority=3
Desktop: Xfce 4.14.3 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: P8Z77-V PRO v: Rev 1.xx serial: <filter>
UEFI: American Megatrends v: 2104 date: 08/13/2013
CPU:
Info: Quad Core model: Intel Core i5-3570K bits: 64 type: MCP
arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21
L2 cache: 6 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27208
Speed: 4400 MHz min/max: 1600/4400 MHz Core speeds (MHz): 1: 4400 2: 4400
3: 4400 4: 4400
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI
driver: nvidia v: 455.45.01 alternate: nouveau,nvidia_drm bus ID: 01:00.0
chip ID: 10de:13c2
Display: x11 server: X.Org 1.20.10 driver: nvidia display ID: :0.0
screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 445x278mm (17.5x10.9")
s-diag: 525mm (20.7")
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
Device-2: NVIDIA GM204 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fbb
Sound Server: ALSA v: k5.4.85-1-MANJARO
Network:
Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe
driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:19.0 chip ID: 8086:1503
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: ASUSTeK
driver: ath9k v: kernel port: d000 bus ID: 07:00.0 chip ID: 168c:0032
IF: wlp7s0 state: down mac: <filter>
Drives:
Local Storage: total: 7.97 TiB used: 7.21 TiB (90.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD30EZRZ-00GXCB0
size: 2.73 TiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
serial: <filter> rev: 0A80
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD30EZRZ-00GXCB0
size: 2.73 TiB block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
serial: <filter> rev: 0A80
ID-3: /dev/sdc maj-min: 8:32 vendor: A-Data model: SP920SS size: 238.47 GiB
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter>
rev: 1.09
ID-4: /dev/sdh maj-min: 8:112 type: USB vendor: MaxDigital
model: MD32500G SATA size: 2.27 TiB block size: physical: 4096 B
logical: 512 B serial: <filter> rev: 8102
Partition:
ID-1: / raw size: 48.83 GiB size: 47.81 GiB (97.92%) used: 10.24 GiB (21.4%)
fs: ext4 dev: /dev/sdc3 maj-min: 8:35
ID-2: /boot/efi raw size: 501 MiB size: 500 MiB (99.80%)
used: 312 KiB (0.1%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sdc2 maj-min: 8:34
Sensors:
System Temperatures: cpu: 46.0 C mobo: 29.0 C gpu: nvidia temp: 38 C
Fan Speeds (RPM): cpu: 871 fan-1: 0 fan-3: 0 fan-4: 1439 fan-5: 0
gpu: nvidia fan: 0%
Power: 12v: N/A 5v: N/A 3.3v: 3.28 vbat: 3.30
Info:
Processes: 209 Uptime: 19m wakeups: 0 Memory: 15.58 GiB
used: 4.55 GiB (29.2%) Init: systemd v: 247 Compilers: gcc: 10.2.0 Packages:
pacman: 1121 lib: 353 Shell: Bash v: 5.1.0 running in: xfce4-terminal
inxi: 3.2.01
Развернуть
journalctl -x -p3 -b1
[ 0.235221] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.962444] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.962456] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 0.964467] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.964479] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 0.965330] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.965341] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 0.965646] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.965658] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 0.967772] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.967783] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 0.968416] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 0.968426] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.807869] vboxdrv: loading out-of-tree module taints kernel.
[ 1.834980] VBoxNetAdp: Successfully started.
[ 1.836427] VBoxNetFlt: Successfully started.
[ 2.027424] nvidia: module license 'NVIDIA' taints kernel.
[ 2.027426] Disabling lock debugging due to kernel taint
[ 2.173572] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020
[ 2.233849] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20190816/utaddress-204)
[ 2.233855] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20190816/utaddress-204)
[ 2.233857] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 2.233859] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20190816/utaddress-204)
[ 2.233860] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 2.233862] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20190816/utaddress-204)
[ 2.233863] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190816/utaddress-204)
[ 2.233865] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 4.078030] proc: Bad value for 'hidepid'
[ 5.338329] kauditd_printk_skb: 10 callbacks suppressed
[ 5.362930] proc: Bad value for 'hidepid'
[ 5.434855] proc: Bad value for 'hidepid'
[ 5.773324] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[ 5.773470] caller _nv000709rm+0x1af/0x200 [nvidia] mapping multiple BARs
[ 12.088040] kauditd_printk_skb: 16 callbacks suppressed
[ 22.221538] kauditd_printk_skb: 8 callbacks suppressed
[ 37.077299] .ready
[ 38.864585] sd 9:0:0:0: [sdh] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[ 155.303378] SUPR0GipMap: fGetGipCpu=0x1b
[ 161.317877] vboxdrv: 000000000405fa6e VMMR0.r0
[ 161.395282] vboxdrv: 0000000079a2f0b4 VBoxDDR0.r0
[ 161.467843] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[evgeny@evgeny-pc ~]$ journalctl -x -p3 -b1
-- Journal begins at Thu 2020-12-03 22:23:39 MSK, ends at Sun 2021-01-03 01:12:06 MSK. --
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:23:39 evgeny-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
дек 03 22:23:39 evgeny-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
дек 03 22:24:26 evgeny-pc lightdm[913]: gkr-pam: unable to locate daemon control file
дек 03 22:24:53 evgeny-pc pulseaudio[1001]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
дек 03 22:25:36 evgeny-pc lightdm[1360]: gkr-pam: unable to locate daemon control file
дек 03 23:40:06 evgeny-pc lightdm[2916]: gkr-pam: unable to locate daemon control file
дек 04 00:02:05 evgeny-pc sudo[33139]: pam_unix(sudo:auth): conversation failed
дек 04 00:02:05 evgeny-pc sudo[33139]: pam_unix(sudo:auth): auth could not identify password for [evgeny]
дек 04 00:02:05 evgeny-pc sudo[33223]: pam_unix(sudo:auth): conversation failed
дек 04 00:02:05 evgeny-pc sudo[33223]: pam_unix(sudo:auth): auth could not identify password for [evgeny]
дек 04 00:53:54 evgeny-pc systemd-coredump[78921]: Process 78916 (xfce4-color-set) of user 1000 dumped core.
Stack trace of thread 78916:
#0 0x00007f0560742b3d g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x34b3d)
#1 0x00007f056072d636 g_object_unref (libgobject-2.0.so.0 + 0x1f636)
#2 0x00005575c1b40398 n/a (xfce4-color-settings + 0x5398)
#3 0x00007f0560ad0249 n/a (libgtk-3.so.0 + 0x84249)
#4 0x00007f056073d98a g_signal_emit_valist (libgobject-2.0.so.0 + 0x2f98a)
#5 0x00007f056073db00 g_signal_emit (libgobject-2.0.so.0 + 0x2fb00)
#6 0x00007f0560d96a75 n/a (libgtk-3.so.0 + 0x34aa75)
#7 0x00007f0560e3cf07 n/a (libgtk-3.so.0 + 0x3f0f07)
#8 0x00007f0560e41478 n/a (libgtk-3.so.0 + 0x3f5478)
#9 0x00007f05609d654f n/a (libgdk-3.so.0 + 0x8954f)
#10 0x00007f05609da12f n/a (libgdk-3.so.0 + 0x8d12f)
#11 0x00007f056097e15b gdk_display_get_event (libgdk-3.so.0 + 0x3115b)
#12 0x00007f05609d9e44 n/a (libgdk-3.so.0 + 0x8ce44)
#13 0x00007f056061b914 g_main_context_dispatch (libglib-2.0.so.0 + 0x52914)
#14 0x00007f056066f7d1 n/a (libglib-2.0.so.0 + 0xa67d1)
#15 0x00007f056061ae63 g_main_loop_run (libglib-2.0.so.0 + 0x51e63)
#16 0x00007f0560c2d4ff gtk_main (libgtk-3.so.0 + 0x1e14ff)
#17 0x00005575c1b3f346 n/a (xfce4-color-settings + 0x4346)
#18 0x00007f0560428152 __libc_start_main (libc.so.6 + 0x28152)
#19 0x00005575c1b3f38e n/a (xfce4-color-settings + 0x438e)
Stack trace of thread 78917:
#0 0x00007f05604f546f __poll (libc.so.6 + 0xf546f)
#1 0x00007f056066f75f n/a (libglib-2.0.so.0 + 0xa675f)
#2 0x00007f056061a121 g_main_context_iteration (libglib-2.0.so.0 + 0x51121)
#3 0x00007f056061a172 n/a (libglib-2.0.so.0 + 0x51172)
#4 0x00007f0560648ce1 n/a (libglib-2.0.so.0 + 0x7fce1)
#5 0x00007f055fafc3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007f0560500293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 78918:
#0 0x00007f05604f546f __poll (libc.so.6 + 0xf546f)
#1 0x00007f056066f75f n/a (libglib-2.0.so.0 + 0xa675f)
#2 0x00007f056061ae63 g_main_loop_run (libglib-2.0.so.0 + 0x51e63)
#3 0x00007f0560869fe8 n/a (libgio-2.0.so.0 + 0x101fe8)
#4 0x00007f0560648ce1 n/a (libglib-2.0.so.0 + 0x7fce1)
#5 0x00007f055fafc3e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007f0560500293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 78919:
#0 0x00007f05604fad5d syscall (libc.so.6 + 0xfad5d)
#1 0x00007f05606688bb g_cond_wait_until (libglib-2.0.so.0 + 0x9f8bb)
#2 0x00007f05605eb813 n/a (libglib-2.0.so.0 + 0x22813)
#3 0x00007f05605eb9a4 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x229a4)
#4 0x00007f056064bc3a n/a (libglib-2.0.so.0 + 0x82c3a)
#5 0x00007f0560648ce1 n/a (libglib-2.0.so.0 + 0x7fce1)
#6 0x00007f055fafc3e9 start_thread (libpthread.so.0 + 0x93e9)
#7 0x00007f0560500293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 78916 (xfce4-color-set) reset memory dump
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░░ Process 78916 (xfce4-color-set) ended due to a critical error.
░░░ A memory dump is written.
░░
░░░ It was probably caused by an error in the program code.
░░░ It is recommended to inform its developers about the problem.
Dec 04 01:27:14 evgeny-pc kernel: watchdog: watchdog0: watchdog did not stop!So far, I have a suspicion that it is a problem with my RAM.
What should my next steps be?
Last edited by Ratcatcher (2021-01-09 03:34:30)
Offline
#2 2021-01-09 12:59:46
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 11,486
Re: xfce4-color-set | software or hardware problem?
Hello and welcome.
дек 04 00:53:54 evgeny-pc systemd-coredump[78921]: Process 78916 (xfce4-color-set) of user 1000 dumped core.
The xfce4-color-set crash is probably not the cause of your freeze. However, with respect to the coredump, do you have xiccd installed?
There is also this existing bug report that looks similar.
So far, I have a suspicion that it is a problem with my RAM.
Have you tested the RAM using something like memtest?
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#3 2021-01-09 13:12:33
- Ratcatcher
- Member
- Registered: 2021-01-09
- Posts: 4
Re: xfce4-color-set | software or hardware problem?
ToZ wrote:
However, with respect to the coredump, do you have xiccd installed?
Yes, but without profiles.
ToZ wrote:
Have you tested the RAM using something like memtest?
Yes, several times and results with no errors.
Offline
#4 2021-01-09 13:36:49
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 11,486
Re: xfce4-color-set | software or hardware problem?
My next guess would be something related to nvidia/intel graphics combination that you have and the nvidia driver you are using. Unfortunately, I have no experience with that combination. Here is the Arch Wiki NVIDIA/Optimus page. Perhaps start there.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#5 2021-01-09 13:39:50
- Ratcatcher
- Member
- Registered: 2021-01-09
- Posts: 4
Re: xfce4-color-set | software or hardware problem?
ToZ wrote:
My next guess would be something related to nvidia/intel graphics combination that you have and the nvidia driver you are using. Unfortunately, I have no experience with that combination. Here is the Arch Wiki NVIDIA/Optimus page. Perhaps start there.
No, Intel is CPU only. I also tried using Nouveau and proprietary drivers, but in both cases I get freezes sometimes.
Offline
#6 2021-01-09 13:53:05
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 11,486
Re: xfce4-color-set | software or hardware problem?
Sorry my bad. I thought I saw an Intel GPU as well.
*gives head a shake*
How often do these freezes happen?
Is this a once in a couple of days total freeze and hang, or intermittent hangs every few seconds?
If the first, then are the logs you've posted from the time of the freeze hang? There don't seem to be any messages indicating a hang.
Does the xfce4-color-set crash happen right at the time of the freeze?
If the second, then have a look at https://forum.xfce.org/viewtopic.php?id=13233 for some info on different vblank methods.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#7 2021-01-09 14:01:15
- Ratcatcher
- Member
- Registered: 2021-01-09
- Posts: 4
Re: xfce4-color-set | software or hardware problem?
Total freeze for a few days, 2-7 days uptime, sometimes can move the cursor, sometimes nothing.
I need to keep a closer eye on the logs, there are no others at the moment.
So far I have tried resetting the bios and using other settings. I will keep an eye on it.
Offline
Pages: 1
- Registered users online in this topic: 0, guests: 1
- [Bot] ClaudeBot
[ Generated in 0.010 seconds, 7 queries executed - Memory usage: 637.35 KiB (Peak: 658.73 KiB) ]