keshavbhatt / whatsie

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

Broken with memory leak #194

Open Shanespeed opened 2 months ago

Shanespeed commented 2 months ago

First of all, thank you for making this lovely application, been using it without any issues until now.

Today I noticed that my desktop suddenly froze up with small gaps of minor responsiveness. After opening the system monitor I noticed Whatsie was using 10% cpu and 12 gigs of ram. After reopening Whatsie I notice that it loads my chats, but I can't send any messages. Checking the system monitor again it consumes between 6 and 20% cpu and steadily increases the ram usage.

Whatsie debug info: Version: 4.15.3 Source Branch: HEAD Commit Hash: 5afb839 Build Datetime: Thu Aug 1 20:47:50 2024 Qt Runtime Version: 5.15.10 Qt Compiled Version: 5.15.10 System: KDE Flatpak runtime Architecture: x86_64 Install mode: flatpak

OS info: Kubuntu 24.04 LTS KDE Frameworks 5.115.0 KDE Plasma 5.27.11 Linux 6.8.0-41-generic

Hardware info: Ryzen 7 2700X (overclocked) Radeon RX 7900 XT 2x8 DDR4-3200 OS and Whatsie installed on the same NVME SSD

If any more information is required I will be happy to help, though I might need some guidance with providing it given I am fairly new to Linux

gedankenstuecke commented 2 months ago

Glad to see it's not necessarily just me @Shanespeed, I've run into the same issue on my Ubuntu install (debug info below)

WhatSie
Version: 4.15.3
Source Branch: main
Commit Hash: 5afb839
Build Datetime: Thu Aug 1 20:41:56 2024
Qt Runtime Version: 5.15.4
Qt Compiled Version: 5.15.4
System: Ubuntu Core 20
Architecture: x86_64
Install mode: snap

And also appreciate all the work that goes into making Whatsie :heart:

gedankenstuecke commented 2 months ago

@Shanespeed fwiw, it seems logging out of WhatsApp within Whatsie and then restarting it at least temporarily resolved the problem of not being able to properly load and send messages.

ratio91 commented 3 weeks ago

same issue. couldn't even logout properly, had to force close it. logging in again solved it for now, but this honestly sucks as I had to re-type several msg again.