-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Random freeze and crash when opening the media viewer in the Linux version #29329
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
Comments
Provide a crash ID |
This also happens on my system, Fedora 42 on Wayland. Since I only just enabled the beta versions in the settings, I can't access the crash reporter and get the crash ID yet. I also don't know how to reproduce the crash at will, it only happens sometimes. Usually at that point the app has already been running at least for a day or so. |
I forgot to say, this bug is random. |
This doesn't remove crash ID requirement |
@ilya-fedin @Aokromes How can I find the Crash ID on the log? I suspect that this bug can be triggered when you suspend the Linux distribution with Telegram running. |
I forgot to say, the Flatpak version is also affected. |
It's not in the log. As described when you was creating issue, it's shown in crash report window which gets activated by "Install beta version" option. |
@ilya-fedin It crashed with this option enabled and didn't shown the crash report window. |
Are you sure? It gets shown on next start |
@ilya-fedin Yes, it crashed two times. |
Well, you can try to find the dumps manually in ~/.local/share/TelegramDesktop/tdata/dumps and upload the related ones here in an archive. Sort them by creation date, check that the last one(s) is new enough to be related and upload it. |
@ilya-fedin There's no dump from today. |
Are you sure what happens is a crash? Maybe the process gets killed by something? |
@ilya-fedin I suspect that it is what happens, what can force Linux to do this? |
Well, maybe tdesktop consumes too much memory or your graphics driver misbehaves (typically happens with proprietary NVIDIA driver) |
@ilya-fedin I know that Linux has a history of crashes when the program memory is paused for suspension or hibernation. Maybe it's related. |
The issue is not actionable without a dump or crash id, sorry |
@ilya-fedin Lack of memory is not the problem (I have 16GB), the Telegram media viewer would need to instantly allocate GBs of data but the GNOME notification don't say that the process was killed because of high memory consumption. I use the open-source AMD driver. |
@ilya-fedin My friend is trying to help me to obtain it. |
If you have a powerful PC, you can try to build tdesktop yourself and run the debug build in gdb. Running the release build in gdb sadly will just result in n/a frames. |
I do have dumps for the crash issue on my system, here's the latest one: 27f1da4e-b810-405c-5ee3e0ae-a600ec40.zip |
Uh oh!
There was an error while loading. Please reload this page.
Steps to reproduce
Expected behaviour
Don't freeze and crash the program.
Actual behaviour
Random freeze and crash the program.
Operating system
Fedora 41
Version of Telegram Desktop
5.14.3
Installation source
Static binary from official website
Crash ID
None
Logs
The text was updated successfully, but these errors were encountered: