search

keshavbhatt / whatsie

Feature rich WhatsApp Client for Desktop Linux
MIT License
1.98k stars 59 forks source link

OOM? Whatsie performs several GCs and interrupts then #185

Open reuschling opened 3 months ago

reuschling commented 3 months ago

I have the issue that whatsie interrupts (I think of low ram), but there is plenty of free ram left on the system. It happens after an hour running, approximately:

whatsie Sandboxing disabled by user.

<--- Last few GCs --->

[72879:0x4e100000000] 2320703 ms: Scavenge 3823.9 (3971.0) -> 3823.8 (3971.0) MB, 90.5 / 0.3 ms (average mu = 0.819, current mu = 0.818) allocation failure [72879:0x4e100000000] 2320791 ms: Scavenge 3823.9 (3971.0) -> 3823.8 (3971.0) MB, 86.9 / 0.4 ms (average mu = 0.819, current mu = 0.818) allocation failure [72879:0x4e100000000] 2320878 ms: Scavenge 3823.9 (3971.0) -> 3823.8 (3971.0) MB, 87.5 / 0.3 ms (average mu = 0.819, current mu = 0.818) allocation failure

<--- JS stacktrace --->

fish: Job 1, 'whatsie' terminated by signal SIGABRT (Abort)

It is the current version in Manjaro AUR, whatsie 4.15.0-1

I have a similar issue by loading web.whatsapp.com with chromium where I get the message that there are is no memory left on the device. Thus, I think of a problem with web.whatsapp.com now.

I disabled background synchronization but it makes no difference.

Maybe someone has an idea?