Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing endlessly on macOS Sonoma 14. #28900

Open
issiueguy opened this issue Jan 26, 2025 · 9 comments
Open

Crashing endlessly on macOS Sonoma 14. #28900

issiueguy opened this issue Jan 26, 2025 · 9 comments
Labels

Comments

@issiueguy
Copy link

Steps to reproduce

Open Telegram, and shortly after, it crashes

Expected behaviour

It was supposed to work properly

Actual behaviour

The program crashes shortly after launching on macOS, with the mouse turning into the spinning rainbow wheel. It is completely unusable, and this issue has been occurring since version 5.10.5

Operating system

macOS Sonoma 14.1

Version of Telegram Desktop

5.10.6

Installation source

Static binary from official website

Crash ID

No response

Logs

@Aokromes
Copy link
Collaborator

plz try to enable beta, restart telegram and send crash id on next start and post id here.

@john-preston
Copy link
Member

Hi. Can you please specify, does it "crash" (closes abruptly) or does it "freeze" (spins the mouse and stops responding, and only way to Quit is from Dock choos Quit Telegram while seeing "not responding" state in the app Dock menu)?

  1. If it crashes - please enable "Install beta versions" in Settings > Advanced, then make it crash and after relaunch agree to send the crash report, also please copy "Crash ID" from the submit report window and copy it here.

  2. If it freezes - please enable "Install beta versions" in Settings > Advanced, then make it freeze and open Terminal, find Telegram pid (process id) in Activity Monitor, type in Terminal "kill -SIGSEGV [pid]" and hit Enter - if it doesn't quit the frozen Telegram, type it again and run the command second time, then it should be killed, invoking a fake crash, after that relaunch the app and agree to send the crash report, also please copy "Crash ID" from the submit report window and copy it here.

Thank you.

@issiueguy
Copy link
Author

Sorry I didn't describe it clearly, it's the second situation - freezes. Here's the crash ID: 38253dbd-aade-4baa-ae32-eb81ee8f1536

@john-preston
Copy link
Member

@issiueguy That's weird, it doesn't parse the dump with my symbols :(

Do you use TDesktop in default way, like copied to /Applications and with default work folder, without any TelegramForcePortable folder creation etc?

Can you please try placing the fresh-downloaded app from https://desktop.telegram.org, put in /Applications, reproduce in that app and do the report once again.

@issiueguy
Copy link
Author

Yes, I've downloaded it several times from https://desktop.telegram.org/ or GitHub, and using the default /Applications always reproduces the freezes. Currently I'm using the App Store version which works fine. Also, I know other people experiencing the same issue. I'll ask them to reproduce and submit reports later.

@john-preston
Copy link
Member

@issiueguy Store version won't save you really, because it's just behind on the updates. So it's better to debug and fix that problem, otherwise store version will get the same problem 😭

I'll ask one more thing, because I'm almost sure where this problem comes from, but I can't reproduce it myself. Do you have some non-default notification sound set up for your account? I'm almost sure the problem arises in preparing the notification sound for the native notifications system (before it was not used, sound was played by the app itself).

If you do have a non-default notification sound I'd ask you to contact me at t.me/preston and send me the exact file that is used for your notifications.

@issiueguy
Copy link
Author

@john-preston Ah, indeed there is a non-default sound source being used for notifications, and the person experiencing the same issue as me also has this. Then we can almost certainly confirm this is the issue!I'll send it to you now!

@issiueguy
Copy link
Author

@john-preston https://desktop.telegram.org/ v5.10.6 crash ID d62d9075-c69c-456e-9183-7c08b3c73876 just sent

@tcitds1
Copy link

tcitds1 commented Jan 27, 2025

Hi. Can you please specify, does it "crash" (closes abruptly) or does it "freeze" (spins the mouse and stops responding, and only way to Quit is from Dock choos Quit Telegram while seeing "not responding" state in the app Dock menu)?

  1. If it crashes - please enable "Install beta versions" in Settings > Advanced, then make it crash and after relaunch agree to send the crash report, also please copy "Crash ID" from the submit report window and copy it here.
  2. If it freezes - please enable "Install beta versions" in Settings > Advanced, then make it freeze and open Terminal, find Telegram pid (process id) in Activity Monitor, type in Terminal "kill -SIGSEGV [pid]" and hit Enter - if it doesn't quit the frozen Telegram, type it again and run the command second time, then it should be killed, invoking a fake crash, after that relaunch the app and agree to send the crash report, also please copy "Crash ID" from the submit report window and copy it here.

Thank you.

Hello,
I'm experiencing the same freezing issue, and it's occurring very frequently (every 1-3 minutes). Due to this, I've had to switch back to using the App Store version.
I've submitted two crash reports after following the freeze reporting procedure:

Crash ID: 81cb488b-62b1-4bf0-8624-531da31ca39c
Crash ID: c78ee30e-8930-4ad3-b95a-1653846d6feb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants