Platform: Windows Desktop (Telegram Desktop 7.0.2, x64)
Bug summary:
App crashes with SIGSEGV when opening a chat with a large number of unread messages (~160 unread).
Steps to reproduce:
Have a chat with a large amount of unread messages (100+) accumulated
Open that chat in Telegram Desktop
App crashes immediately (jump-to-unread logic seems to trigger it)
Workaround found:
Marking the chat as read from another device (mobile) before opening it in Desktop prevents the crash — the chat opens fine at the bottom of history without the crash.
Additional info:
Tried disabling GPU rendering (ANGLE backend set to "Disabled" in Advanced Settings) — crash still occurred, so it's not GPU/rendering related.
Cleared local cache — did not help.
Crash type: SIGSEGV (confirmed via Google Breakpad minidump)
Two minidump IDs captured: 9ded1392-aaa3-4e6c-a10a-d9e087fae54c and 4b81194f-9745-4de9-8ede-3093fc4a8164
Steps to reproduce
1)Accumulate a large number of unread messages in a chat (~100+, I had 160).
2)Open Telegram Desktop with that chat still unread.
3)Click on the chat to open it.
4)The app crashes immediately (SIGSEGV) — appears to happen during jump-to-unread rendering.
Note: If the chat is marked as read from another device (e.g. mobile) before opening it in Desktop, it opens fine at the bottom of history without crashing. This confirms the crash is tied to the "jump to first unread message" logic, not the chat content itself.
Hello, thanks for the card. We need some additional information to investigate the problem further. Could you please contact support here t.me/+42439? Then select "Skip and proceed to volunteers" using the bot's buttons and send a #c63815 tag to the chat. Our volunteers will be in touch shortly.