Telegram crashes when typing a capital letter O into any chat.

[gsuberland]

Steps to reproduce

1. Type a capital letter O in any message.
2. Telegram crashes.

This is reproducible on my desktop. The first instance of it showed up on 2017-12-11. Cannot reproduce on another system.

I have tried all other letters and it is only a capital O (shift+o) that does it. Either shift key will do it.

This is honestly the weirdest bug I've ever reported to anyone.

Expected behaviour

Types a letter 'O'.

Actual behaviour

Crash.

Configuration

Operating system: Windows 10 x64

Version of Telegram Desktop: 1.2.6

Used theme: Whatever the default is.

Keyboard: QWERTY, UK layout.

Logs

Logs and crash dump:

• crashdump.zip
• log_17_00.txt
• mtp_17_00.txt
• tcp_17_00.txt

[gsuberland]

EIP is 00000000 for one thread. ESP and EBP look sane but there's no memory at those addresses. Something accidentally freed the stack, perhaps? Very odd.

[john-preston]

@gsuberland If you relaunch the app after crash does it offer you to send a crash report? If not please download the portable alpha version from https://desktop.telegram.org/changelog#alpha-version launch it, autoupdate it in Settings to 1.2.6 and reproduce the crash. After relaunch it should offer you to send a crash report. Please copy the Crash Report Tag here and submit the report.

[gsuberland]

I get a "Telegram didn't close properly" window on restarting the application, but it does not offer an option to send a crash report, nor did the alpha version offer to send a crash report.

[john-preston]

@gsuberland If alpha version doesn't offer to send a report it means that it wasn't even catched. Are there any dumps in the "tdata/dumps" folder near Telegram.exe file?

[gsuberland]

@john-preston Yes. I attached the crash dump in a zip with the original report (crashdump.zip)

Here's another eight to play with: crashdumps.zip

[gsuberland]

Well, I think I found the problem...

Looks like NZXT's (incredibly crappy) CAM software, that I am unfortunately forced to use to control my water cooler, is injecting a thread into processes in order to monitor FPS or some other nonsense. Taking a look at the default settings makes it obvious why the crash occurs when shift+o is pressed:

Disabling CAM Overlay fixes the bug. I would take this up with them, but NZXT are terrible for listening to any kind of criticism over CAM.

[john-preston]

Yeah, those dumps give me nothing :(

[gsuberland]

@john-preston See above reply - I worked it out with a live debug session.

[github-actions]

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.