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

Crash on OSX when viewing a message containing "\u180e\u2061" in code or pre tags #4551

Closed
udf opened this issue Mar 30, 2018 · 2 comments · Fixed by AndroidKotlinID/tdesktop#54

Comments

@udf
Copy link
Contributor

udf commented Mar 30, 2018

Steps to reproduce

  1. Copy and send the following text in a message (surround it in ``):
    ]᠎⁡[
    (there are two zero width characters between the "]" and "[")
  2. View the message from tdesktop on OSX

Additionally, you can swap the order of the two zero width characters and it still crashes. If the message is deleted in a supergroup, viewing the admin log causes the same crash.

Expected behaviour

The chat where the message was sent can be read as normal.

Actual behaviour

tdesktop crashes. The message has to be deleted to make tdesktop usable again.

Configuration

Operating system: Mac OS X 10.13.4

Version of Telegram Desktop: 1.2.15

Used theme: Default

A crash report is attached as the logs don't seem to contain anything useful.
Telegram_2018-03-30-144411_Yoricks-MacBook-Pro.crash.txt

@john-preston
Copy link
Member

john-preston commented Mar 30, 2018

@udf Thanks, it crashes me even through GitHub bot message with your report 🙈

@github-actions
Copy link

github-actions bot commented Mar 7, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants