Media files sometimes take very long time to download or upload

[gmk57]

Steps to reproduce

1. Open chat with unread images / video
2. Sometimes they load very quickly, sometimes take >15 minutes

Internet connection is 100 Mbit/s wired, there are no issues with other internet services.

This started happening after upgrading from 2.1.7 from Ubuntu repositories (after it started nagging me with "this version is not supported" messages) to 3.2.* from official website. Still happens on 3.4.*.

Expected behaviour

Media files should load quickly

Actual behaviour

Indefinite load spinners are shown

Operating system

Linux Mint 20.2 Cinnamon

Version of Telegram Desktop

3.4.3

Installation source

Static binary from official website

Logs

[2022.01.06 14:11:20] OpenGL: [TRUE] (OverlayWidget)
[2022.01.06 14:11:20] Using SNI tray icon.
[2022.01.06 14:16:02] RPC Error: request 45 got fail with code 400, error PEER_ID_INVALID

(there is nothing more in the log.txt, even after images loaded successfully)

[robme]

I have been experiencing the same in the last day. Many images don't seem to load at all. Some still load instantly.

On Windows desktop.

In my log this error happens whenever an image doesn't load:

[2022.01.07 20:11:46] RPC Error: request 1285 got fail with code 400, error CHAT_ADMIN_REQUIRED
[2022.01.07 20:15:15] RPC Error: request 1308 got fail with code 400, error CHAT_ADMIN_REQUIRED
[2022.01.07 20:15:35] RPC Error: request 1396 got fail with code 400, error CHAT_ADMIN_REQUIRED
[2022.01.07 20:16:05] RPC Error: request 1419 got fail with code 400, error CHAT_ADMIN_REQUIRED

[robme]

Seems to be working normally for me now, so perhaps this was a temporary server issue.

[gmk57]

It happens to me again:

[2022.01.14 23:15:12] RPC Error: request 68 got fail with code 400, error PEER_ID_INVALID
[2022.01.14 23:17:19] RPC Error: request 125 got fail with code 400, error PEER_ID_INVALID
[2022.01.14 23:17:21] RPC Error: request 144 got fail with code 400, error PEER_ID_INVALID
[2022.01.14 23:17:39] RPC Error: request 157 got fail with code 400, error PEER_ID_INVALID
[2022.01.14 23:20:42] RPC Error: request 174 got fail with code 400, error PEER_ID_INVALID
[2022.01.14 23:21:11] RPC Error: request 185 got fail with code 400, error PEER_ID_INVALID

After waiting ~20 minutes the image was loaded successfully.

[gmk57]

Now a couple of images doesn't upload.

[2022.01.29 10:35:26] RPC Error: request 47 got fail with code 400, error PEER_ID_INVALID
[2022.01.29 10:55:41] RPC Error: request 122 got fail with code 400, error PEER_ID_INVALID
[2022.01.29 10:55:58] RPC Error: request 136 got fail with code 400, error PEER_ID_INVALID

After ~10 minutes waiting I had to restart Telegram and re-send them.

[gmk57]

This happens repeatedly today in Telegram Desktop 3.5.1, I've already restarted it twice, and it still doesn't download/upload files without very long delays. And I don't see any RPC Error messages in log.txt in the last half an hour, so maybe they're not related after all.

[robme]

It's actually still happening to me occasionally, but I don't necessarily see an error in the log. I wonder if it's just network congestion. Sometimes certain images show a loading circle forever and won't load, but if I come back after a few hours they all load instantly like normal.

[gmk57]

Personally, I don't believe in a network congestion in a 100 Mbit/s wired network, so severe that transferring ~200Kb image takes 10-20 minutes. ;) Telegram on Android, connected by WiFi to the same router, loads the same images instantly.

Another strange symptom: while the chat to which I'm trying to send (or view) an image is opened in Telegram, it constantly consumes ~15% of my six-core processor. Does it need entire x86 core to draw a loading indicator?

[robme]

I mean on Telegram's servers, not your own internet.

[stale[bot]]

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

[gmk57]

I don't remember seeing this issue in the last couple of months. Not sure what has changed: Telegram app, their servers or maybe something at my internet provider. Probably can be closed for now.