TelegramSwift icon indicating copy to clipboard operation
TelegramSwift copied to clipboard

Very big memory leak

Open fragmential opened this issue 3 years ago • 15 comments

Screenshot 2022-02-17 at 15 26 36 In the past few weeks, every now and then while having telegram open in the background, I will get the notification that I have run out of application memory. And Telegram will have around 100GB of memory used, and it increases very fast (a gigabyte every few seconds)

This has been happening the last few versions, but this is version 8.5.226936 Stable. I am running it on an M1 MacBook Pro with macOS 11.6

I can't explain very precisely how to reproduce it, as it happens seemingly randomly, and usually while I am working in a different application.

fragmential avatar Feb 17 '22 18:02 fragmential

The same just happened to me, 8.5.226936 Stable consumed all available memory 2022-02-18 11 52 16

VladKorzun avatar Feb 18 '22 09:02 VladKorzun

Same happened to me as @diddy0dante M1 Pro '106GB' application out of memory crash 8.5.226936 Stable macOS 12.2.1 (21D62)

dylmanning avatar Feb 25 '22 04:02 dylmanning

M1 Pro Any scroll of chats cause constantly increasing memory size photo_2022-03-24 20 03 44

nexron171 avatar Mar 24 '22 17:03 nexron171

In my case the problem was resolved after upgrading to Monterey 12.2. Looks like it's a bug in MacOS. Now Telegram consumes 500-700mb of ram during the day.

nexron171 avatar Mar 31 '22 11:03 nexron171

photo_2022-04-12 13 10 00 Running the latest version of MacOS Monterey, seems to still be an issue.

System:

  • Macbook Air M1
  • 16 GB Ram
  • MacOS Monterey 12.3.1

dewald-els avatar Apr 12 '22 11:04 dewald-els

Ran into this today. How is this NOT fixed yet?

dereitz avatar Dec 09 '22 20:12 dereitz

Ran into this today. How is this NOT fixed yet?

My guess is that the contributors of this project don't use Apple Silicon Macs and can't reproduce it. It seems everyone here (in this thread) has some variant of M1.

It's notoriously difficult to fix a random memory leak that isn't consistently reproducible with a specific setup.

fragmential avatar Dec 09 '22 21:12 fragmential

Ran into this today. How is this NOT fixed yet?

My guess is that the contributors of this project don't use Apple Silicon Macs and can't reproduce it. It seems everyone here (in this thread) has some variant of M1.

It's notoriously difficult to fix a random memory leak that isn't consistently reproducible with a specific setup.

I should have mentioned this was on a x86-based machine. Specifically, the 2014 iMac Retina 5k, so it doesn't seem to be specific to Apple silicon.

dereitz avatar Dec 09 '22 22:12 dereitz

Oh, interesting. Then I'm surprised no one has figured out the cause yet.

fragmential avatar Dec 10 '22 21:12 fragmential

macOS 12.6.2, MacBook Pro 2019, Intel

Screen Shot 2023-01-22 at 22 52 58

telegram_sample.txt

UPD: Fixed in 9.3.1.242366 Beta (after this commit)

dmemarko avatar Jan 22 '23 21:01 dmemarko

2GB+ RAM usage after opening several chats on MBA M1 16GB

9.3.1.241825 Stable

shpilla avatar Jan 24 '23 15:01 shpilla

Ran into this today. How is this NOT fixed yet?

My guess is that the contributors of this project don't use Apple Silicon Macs and can't reproduce it. It seems everyone here (in this thread) has some variant of M1.

It's notoriously difficult to fix a random memory leak that isn't consistently reproducible with a specific setup.

the thing is, the developer just doesn't give a shit. And somehow it's an official telegram client.

The issue is easily reproducible even on intels, just keep the client open for some time and get a few gigs sucked in.

Haarolean avatar Aug 09 '23 06:08 Haarolean

This issue is still persisted on Sonoma 14.4.

dmko1610 avatar Mar 27 '24 10:03 dmko1610

The same is here. still even in Sequoia (and before on Sonoma); 2-3 gigs for nothing.

This issue is still persisted on Sonoma 14.4.

repentandliveholy avatar Jul 30 '24 20:07 repentandliveholy