Telegram crashes upon clicking on avatars in a group chat
zubozrout opened this issue · comments
Hello,
If I click on an avatar in a group chat Telegram usually crashes.
To reproduce this you need to try hitting the avatars in a chat thread multiple times in the row. Hitting it once usually doesn't crash the app. It can be a bit picky sometimes so if it doesn't crash for one contact, try a different one or click on various avatars randomly.
I am not sure how much the attached log can help but I expect this happens each time I click the profile icon in the chat:
getFile(): Cannot request a file from the server, bogus data provided:
I am on Meizu MX4 arale, Xenial (r95)
I can confirm this bug on BQ E4.5 (krillin) running Ubuntu 16.04 (r95). Clicking repeatedly on the avatars crashes telegram (version 2.5.4.0)
- Unity8.log output https://paste.ubuntu.com/p/sTcbWWznFR/
- application-click-com.ubuntu.telegram_telegram_2.5.4.0.log output https://paste.ubuntu.com/p/dPfHYvrBSG/
This is the event while clicking on avatars:
[20180615 10:29:34.462 CEST qml: dialogIsChannel: true
[20180615 10:29:34.462 CEST qml: megagroup: true
[20180615 10:29:34.655 CEST qml:
Are you talking about the avatars of the group or of users?
@Flohack74 If you select a group chat on the main screen and see the thread of messages then by persistent clicking on avatars next to each message Telegram crashes.
Sorry I cant reproduce this right now. I clicked a lot...
I can confirm this bug is still happening on BQ E4.5 (krillin) running UT 16.04 (2018-06-25).
I can reproduce the crash every time opening a group on Telegram, v.g. the SG, click 2 o 3 times on an avatar there, scroll up, click another avatar repeatedly, scroll again (up or down) click several times again and... crashed.
This seems to be related to calling message_item.dialogRequest in telegram/app/qml/components/MessagesListItem.qml as every time it crashes I can get all the logs here up to this point - nothing after it. Also it looks like it mostly happens if you open a group and scroll up a bit - with the high probability of crashing in this group: UBports QA and testing in contrary to others where it is much harder to reproduce.
Well, considering current Telegram is not in the best shape and there are ambitions too build a new one + the fact tracking this down is not so simple as no logs are being created for this issue maybe it's time to deploy a "Won't fix" label here, close it and be good with it :).