Last time Telegram Desktop was not closed properly

[Dimezis]

Steps to reproduce

1) MacOs 12.5 2) Launch Telegram 3) See a dialog blink for fraction of a second - "Last time Telegram Desktop was not closed properly"

Reinstall and reboot didn't help. The regular dedicated Macos Telegram version works fine. This started happening after today's update to MacOs 12.5

Expected behaviour

Work

Actual behaviour

Crash

Operating system

Macos 12.5

Version of Telegram Desktop

Latest from here https://desktop.telegram.org/

Installation source

Static binary from official website

Logs

For some reason there are no logs in the Console app

[john-preston]

@Dimezis Please try the beta version from https://desktop.telegram.org/changelog#beta-version

[Dimezis]

@john-preston still the same problem unfortunately

[Dimezis]

This time however it shows more info. I also sent the report

ApiId: 2040
Binary: Telegram.app
Launched: 06.08.2022 11:59:37
OpenGL Renderer: [not-initialized]
Platform: MacOS
UserTag: 35002cb3da3d3faf
Username: Dimezis
Version: 4000004 beta
OS-Version: 2113.5999
Caught signal 6 (SIGABRT) in thread 4423435648

Backtrace omitted.

[john-preston]

@Dimezis Please contact me at t.me/preston, I'll ask you to send me .zip-ed folder "~/Library/Application Support/Telegram Desktop/tdata/dumps"

[john-preston]

@Dimezis Please also submit the report and copy the "Your Report Tag" string from the crash report window and post it here.

[Dimezis]

Report tag 96a42322-160d-4d1d-9293-358952166bdc

[Dimezis]

Seem to be caused by this - https://issuehint.com/issue/kovidgoyal/kitty/5302 Works fine without an external monitor or without a custom color profile

[john-preston]

@Dimezis I can't really know how to fix this right now :( Perhaps OpenGL became broken in 12.5 in such setups. Possibly Qt 6.4 with Metal widgets backed is the answer for that. But this is a very new tech, I'm a bit afraid to dive in that right now, this may have huge amount of bugs + requires a lot of rewriting, because right now all hardware-accelerated rendering on all platforms uses OpenGL directly.

[vandpurnama]

I got same problem on linux

Installed using aur package : telegram-desktop-bin Installed version : 4.3.1-1 (Lastest version)

dump core file

[Aokromes]

I got same problem on linux

Installed using aur package : telegram-desktop-bin Installed version : 4.3.1-1 (Lastest version)

dump core file

plz try downloading official version (non snap, non flakpak) from https://desktop.telegram.org

[vandpurnama]

I got same problem on linux Installed using aur package : telegram-desktop-bin Installed version : 4.3.1-1 (Lastest version) dump core file

plz try downloading official version (non snap, non flakpak) from https://desktop.telegram.org

i'm installing directly from aur package... it's desktop native that clone and build from this repo release and it's not from snap or flakpak version

is this repo release different from https://desktop.telegram.org release ?

[Aokromes]

I got same problem on linux Installed using aur package : telegram-desktop-bin Installed version : 4.3.1-1 (Lastest version) dump core file

plz try downloading official version (non snap, non flakpak) from desktop.telegram.org

i'm installing directly from aur package... it's desktop native that clone and build from this repo release and it's not from snap or flakpak version

is this repo release different from desktop.telegram.org release ?

arch packages are known causing issues official versions don't have, that's why i ask you to try static binary instead.

[vandpurnama]

nope still error and got force close

terminal log : terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped)

[periwinkleFTW]

Have the same error for all of november 2022. annoying af. Redownloaded and reinstalled latest version. Still the same error

[Chupaka]

MacOS 13.0.1 here. TD is working in background and then sometimes disappears w/o any messages. When I launch it, it shows the same window with "last time telegram desktop was not closed properly" message.

I checked ~/Library/Application Support/Telegram Desktop/tdata/dumps/completed folder - since Oct 26 I have almost 70 dumps, sometimes several times a day.

[BotBY]

It's the same for me. Almost every time I close the lid of my macbook Telegram closes with an error

[Flake174]

Hello! I had the same problem. The following steps helped me

1. Terminate desktop session throught mobile app
2. Open desktop version, wait for login screen
3. Close desktop app(important!)
4. Open desktop app again and log in

After that app stopped crashing

[ederdeivid]

Try this following steps:

WINDOWS: 1- Windows key > type "Telegram" > Right Click > Go to file location 1.1 - Right click on Telegram shortcut > Go to file location (once again)

Now you are in the real file location

2- GO TO: tdata > userdata > cache > (select your cache folder) > CTRL + A (there are a lot of folders, right?_) > SHIFT + DEL > Confirm > Relaunch

LINUX idk

[BotBY]

@john-preston Any updates? It's been almost a year now.

[ilya-fedin]

@BotBY wasn't this fixed on macOS side?

[BotBY]

@ilya-fedin No. In spite of all the macOS (Intel) and Telegram updates I still get this error

[ilya-fedin]

I guess this won't be solved any time soon as first Qt version with Metal support for widgets is 6.4 but its minimal macOS version is 10.14. tdesktop has planned to deprecate 10.12 in July and make 10.13 the minimal supported version. Deprecates are very rare what means tdesktop is blocked on older Qt for multiple next years. The only hope is for this to be solved on macOS side.

[john-preston]

@BotBY Do you have dumps in tdata/dumps/completed after those closings? The same folder that is mentioned in the conversation above.

If you do, please enable installing beta versions in Settings Advanced. After that it should offer you to send crash report after the next crash. Send it and send here the Crash ID from the sending box. Maybe now it gives something fixable 🫣

[informagico]

@john-preston same thing happens to me every time. I'm on macOS 13.4 Beta (22F5027f). Telegram version 4.7.0 (beta enabled)

Crash ID: 11f24154-3d7c-4515-aca4-b55854e69c63

ApiId: 2040
Assertion: "_eventNestingLevel >= _loopNestingLevel" sandbox.cpp:577
Binary: Telegram.app
Launched: 11.04.2023 19:07:54
OpenGL: Enabled
OpenGL Renderer: [not-initialized]
Platform: MacOS
Version: 4007000
OS-Version: 2299.5000
Caught signal 11 (SIGSEGV) in thread 140704440714880

If you need I can share the dumps folder, just let me know where I can reach you.

[BotBY]

@john-preston Crash ID: 5cbfe7ab-4c79-437d-8108-53b99f89e378

[Gennady-G]

This bug is also occurs on Telegram desktop 4.7.1 on Windows Server 2019 (portable telegram version).

If I reinstall full (non-portable) version will it resolve, what do You think?

[ilya-fedin]

@Gennady-G you can't have the problem discussed here, the issue is about a crash on macOS systems with color-managed displays.

[informagico]

@ilya-fedin Sorry for the dumb question, what do you mean with color-managed displays?

[ilya-fedin]

@informagico non-sRGB color profile

[ilya-fedin]

https://github.com/telegramdesktop/tdesktop/issues/24879#issuecomment-1207209923

[ksa-real]

I have official Telegram Desktop 4.8.1 on MacOS and Telegram constantly silently crashes when the laptop gets suspended (lid is closed). I cannot tell when this happens exactly - right after the lid is closed or some other conditions must be met. I have this issue since the upgrade to macOS Ventura. Another family member has the same issue on their laptop.

[dzentota]

I have the same issue as @ksa-real (MacOs Ventura) for a long time

[ksa-real]

Still have the issue on two different Macbooks with Ventura. Almost every time I open the laptop lid, I have to open Telegram again.

[Aokromes]

try with the latest 4.8.9 version.

[ksa-real]

The latest I see in this repo or on the official site is 4.8.8. Where to get it?

[Chupaka]

@Aokromes the same situation on 4.8.9

[ksa-real]

Actually, may be a bit different now. The app crashed a few times during normal work, like switching between windows. Previously I associated the issue with suspend mode / lid closure only.

[github-actions[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!