Telegram Desktop consistently crashes on one specific Telegram account with:
libc++abi: terminating due to uncaught exception of type std::length_error: vector
followed by SIGABRT.
The issue is account-specific.
Reproduction / troubleshooting already performed:
Telegram Desktop 7.2.5 stable reproduces the crash.Telegram Desktop 7.2.6 beta also reproduces it.Tested with a completely clean -workdir and fresh login — still crashes.Tested explicitly with native arm64 on Apple Silicon — still crashes.Another Telegram account on exactly the same Mac, client, network and VPN works normally.Telegram Web works normally with the affected account.The app may stay open initially, but while navigating between chats it eventually crashes. The crash is not tied to one obvious chat or media message.Multiple independent crash dumps reproduce the same crash path.
Environment:
Telegram Desktop 7.2.6 beta
Apple Silicon / arm64
macOS 26.5
Crash:
std::length_error: vector
SIGABRT
I can provide multiple .dmp crash dumps if needed.
Steps to reproduce
Launch Telegram Desktop 7.2.6 beta on macOS 26.5 (Apple Silicon, arm64).Log in to the affected Telegram account using a completely clean profile/workdir.Wait until the chat list finishes loading.Open several normal chats one after another. The chats do not need to contain media; plain text chats are enough.After opening a few chats, Telegram crashes with SIGABRT.Terminal output shows: libc++abi: terminating due to uncaught exception of type std::length_error: vector.
Device info
Telegram Desktop 7.2.5 arm64, MacBook Pro M4, macOS 26.5.1
Additional important detail: this issue affects the same Telegram account across multiple native clients and devices. The affected account crashes Telegram on: macOS, Windows and mobile. Telegram Web continues to work normally. A different Telegram account works normally on the same devices/network. This means the problem is not limited to one OS, one installation, one local profile, or one VPN/network setup. It appears to be tied to account-specific/server-side state that causes native Telegram clients to crash. On macOS, the crash is reproducible and consistently ends with: libc++abi: terminating due to uncaught exception of type std::length_error: vector followed by SIGABRT. At the moment, this makes the affected account effectively unusable in Telegram native clients across all my devices, with Telegram Web being the only usable client.
Admin Dog
Can you provide more details? Is the issue caused by some sticker ?
I think yes, because crashes are stopped. I saw negative messages in some public groups about stickers, so i think it was the issue. I could attach bug dump, but it’s format not supported here
The affected account crashes Telegram on:
macOS, Windows and mobile. Telegram Web continues to work normally.
A different Telegram account works normally on the same devices/network.
This means the problem is not limited to one OS, one installation, one local profile, or one VPN/network setup. It appears to be tied to account-specific/server-side state that causes native Telegram clients to crash.
On macOS, the crash is reproducible and consistently ends with:
libc++abi: terminating due to uncaught exception of type std::length_error: vector
followed by SIGABRT.
At the moment, this makes the affected account effectively unusable in Telegram native clients across all my devices, with Telegram Web being the only usable client.
https://filebin.net/d5k6o9m412lcgph4
I upload files here, is it ok? I could try to pastebin at home