ars3niy / tdlib-purple

libpurple Telegram plugin using tdlib
Other
147 stars 32 forks source link

Eats too much memory in Pidgin #156

Open vondrt4 opened 2 years ago

vondrt4 commented 2 years ago

When loaded into Pidgin, with my Telegram account heavy with Groups, the plugin eats over 700M of memory, while the original Telegram stays within ~300M. Formerly, there used to be a memory leak in Telegram which caused it to slowly grow from its base usage. I had to wrap it in a memory cgroup to protect the rest of the system. They fixed the bug later. Is it possible that it is again present in tdlib? With Pidgin and tdlib-purple, the base usage is around 700M and it runs out of 1G cgroup and 1G swap in under a day, making the solution unusable. Compiled from master for i386.

dilworks commented 2 years ago

Can confirm here: just got enrolled into a local shopping group, quite picture/video heavy, and since I joined it, I've had to deal with frequent memory leaks on Pidgin! (among other issues, but this one being the most serious) - at one point it was eating over FIVE GIGABYTES (and triggering heavy swapping on my 8GB system)

FWIW, I'm using 0.8.1 self-built .DEBs on Debian 10, amd64.

frostmorn commented 2 years ago

Arch Linux, eats allmost all memory on pidgin exit. All windows became frozen on rendering animated stickers, which I suppose `cause of rendering process happens not in a separate thread, have no caching for a stickers allready rendered. Also adding a white background to an animated sticker which I suppose not needed at all. Found that everything's okay if compile with -DNoLottie=True, pidgin eats 150 M of memory and looks that this memory issue doesn't repeat.

Also, on sending somebody a file, this file also trying to be downloaded after sending, which also seemed to be not so okay.