Tdesktop: Telegram hangs on W10 Anniversary Update

Created on 4 Aug 2016 · 52Comments · Source: telegramdesktop/tdesktop

Steps to reproduce

Get a message with notification
Try to interact with the program (while the notification is still on the screen)

Expected behaviour

The program should work normally

Actual behaviour

The program freezes and i have to kill it through task manager

Configuration

Operating system:
W10 x64 Anniversary Update 1607 (14393.10)
Version of Telegram Desktop:
0.10

bug windows

Source

ghost

👍18

Most helpful comment

Can confirm that the issue is still present on 0.10.8 with the latest windows updates installed (KB3194496)

dim5 on 30 Sep 2016

👍3

All 52 comments

@Z3phyr How do you get this update? I'm testing on Win10 Home 64 bit and it works fine.

Does it freeze if you disable "Window toast notifications" in Settings? (and receive a message with a custom app notification — white in the bottom-right corner). Or it freezes only after showing (or trying to show) a windows toast notification?

john-preston on 4 Aug 2016

@john-preston

How do you get this update?

Just in case, it's a new big update. You can download it through control panel ("Update & security") or manually here .

spzSource on 4 Aug 2016

@spzSource System is up to date. Is it one of some Insider Preview builds?

john-preston on 4 Aug 2016

And is it working fine with custom notifications? Hanging only with Windows toast notifications?

john-preston on 4 Aug 2016

@john-preston

System is up to date. Is it one of some Insider Preview builds?

No, the anniversary update is not available for all users yet.

auchri on 4 Aug 2016

it's the latest update from Windows, not an insider build. The issue happens with system notifications I can't test the custom notifications right now, I'll update as soon as possible.

ghost on 4 Aug 2016

@Z3phyr To test the custom notifications you just need to switch off Windows toast notifications in Settings.

john-preston on 4 Aug 2016

^ same thing, but without error code at all :sob:

Brawaru on 4 Aug 2016

@DaFri-Nochiterov I've managed to update it, but in first couple of tests it works fine.

john-preston on 4 Aug 2016

Hi, I have the same exact problem. I clean installed W10 anniversary, installed telegram, and when a message arrives, it often makes Telegram crash. I have to force close it with the task manager. The version of the client is 0.10

ghost on 5 Aug 2016

@marcogiorgio
Does it freeze if you disable "Window toast notifications" in Settings? (and receive a message with a custom app notification — white in the bottom-right corner). Or it freezes only after showing (or trying to show) a windows toast notification?

auchri on 5 Aug 2016

@auchri Yes it happens with "Window toast notifications" on. If I disable it, it all seems normal

ghost on 5 Aug 2016

@marcogiorgio Thanks for the answer, so it seems to be an issue with the windows toast notifications
/cc: @john-preston

auchri on 5 Aug 2016

@auchri I am glad I helped :)

ghost on 5 Aug 2016

👍1

Can confirm this issue has been present since early Insider builds of the Anniversary Update, but only for native toast notifications. It's possible that it's been fixed in the latest update, though, as I wasn't able to reproduce it just now. Normally those notifications crash Telegram quite consistently.

Is it possible this is related to #2318 and the lack of a handler?

Zenexer on 18 Aug 2016

Can also confirm the same exact issue since anniversary update.

sinaa on 18 Aug 2016

Confirmed still an issue with 0.10.2 alpha. Looking to debug. @john-preston

It did eventually recover this time. It also didn't occur until the notification started to disappear.

On repeated tests, sometimes it recovered, sometimes I had to kill the process. One time, when I killed the process and relaunched it, Telegram wasn't scaling properly for my display (it should normally be 200%--250%, actually, but that's not supported). The scaling controls had disappeared from settings. Text and bounding boxes for most controls were the correct size, but the images for them were too small, and mouse events weren't being registered properly for many controls. Some controls were overlapping. Deleting the tdata folder alone didn't work; I had to restart my computer on top of that.

I didn't get to debug it yet, but here's the stack of the main thread at the time:

screenshot 2016-08-20 13 58 52

Here's another thread that was using some CPU (< 1%):

screenshot 2016-08-20 13 59 53

Zenexer on 20 Aug 2016

Not getting anywhere debugging it. As far as I can tell, the window continues to update; it just doesn't respond to any events. There are events coming in from Windows that get processed, but I can't really tell if they're normal. Sometimes when it got stuck the main thread was running MainWindow::shadowsActivate and was busy drawing. Now I can't reproduce that; it's always stuck in the kernel, and Microsoft hasn't released the debug symbols for the Insider preview I'm using. I tried profiling it but didn't see an excessive number of calls to anything at first glance. I can only assuming it's waiting on something that usually never comes.

Zenexer on 21 Aug 2016

👍1

Currently am facing the same issue too.

EDIT: Disabling Windows notifications helped.

yongjunjie on 23 Aug 2016

Same issue for me. Turning off "Use Windows Notifications" seemed to take care of it. Thanks to @john-preston for isolating this issue!

ms82494 on 30 Aug 2016

Still have this issue and it's not fixed even in the new version (0.10.5) yet...!

AliMirlou on 13 Sep 2016

@Alimirlou I can't reproduce that myself, but the collected data shows, that this is some problem inside the Windows notifications methods :(

I've asked about that on the msdn article about the toast notifications, but didn't get any response so far: https://blogs.msdn.microsoft.com/tiles_and_toasts/2015/10/16/quickstart-handling-toast-activations-from-win32-apps-in-windows-10/#comment-4485

Currently I can only suggest you disabling the windows toast notifications in Settings (so you'll get custom telegram notifications instead).

john-preston on 13 Sep 2016

Since I'm on Win10 Anniversary, I got that issue too. I can confirm that disabling Windows notifications got me rid of that issue.

Aenadon on 15 Sep 2016

@john-preston You should ask on the MSDN forums: https://social.msdn.microsoft.com/Forums/

auchri on 15 Sep 2016

Is there an easy way I can log all messages Qt receives from Windows? I played around with various environment variables but couldn't get it working in a useful way, and the lack of kernel debug symbols is making it difficult to trace the problem in Visual Studio.

I suspect the issue might not actually be a problem with Windows, but rather Qt. As far as I can tell, there's still a lot of drawing going on when Telegram freezes. Either messages aren't making it to their proper destinations, or the message loop is getting stuck.

If I get a chance I'll give it a try on my desktop, which is on a stable build of Windows. Until recently, I couldn't actually reproduce it there, but it just started exhibiting this issue a few days ago.

Zenexer on 20 Sep 2016

Can confirm that the issue is still present on 0.10.8 with the latest windows updates installed (KB3194496)

dim5 on 30 Sep 2016

👍3

@dim5 I'm afraid the only thing to do is to disable Windows toast notifications in Settings. They hang the process sometimes (as I see it in logs), no idea what I can do about it.

john-preston on 30 Sep 2016

Still crashes with latest version on a fully updated Windows 10.

VSG24 on 16 Oct 2016

@VSG24 Please try latest alpha version.

john-preston on 16 Oct 2016

👍1

The issue still persists on v0.10.19, and on two of my devices, one using Windows 10 Pro 64bits and the other Windows 10 Education 64bits.

It always happens when the app is minimized and I get a notification from a conversation which isn't the "opened" one.

tgrondier on 25 Oct 2016

Build 14959 no more issue

Marocco2 on 4 Nov 2016

👍1

I'm having this exact issue.... I'll get a message and Telegram will just deadlock ....done...... need to kill the process and restart it.. and I'm running Win10 AUP... It started happening with the latest update.

juniberry on 2 Dec 2016

Yup. I am on the alpha build and this was never fixed for me. I thought an update would arrive with a fix. It never did. I have to keep native notifications disabled because of this issue.

Sushubh on 2 Dec 2016

@Sushubh Yes, because they freeze in Windows :( So I had to disable them by default.

john-preston on 2 Dec 2016

Strange. I have Surface Pro 3 i5 with build 14971 and native notifications don't freeze telegram

Marocco2 on 2 Dec 2016

@Marocco2 It's Insider build, isn't it?

stek29 on 4 Dec 2016

Yes, it is

Marocco2 on 4 Dec 2016

@Marocco2 so it means Microsoft fixed the issue.
But the fix isn't published yet, and majority of users are not Insidersz so it's better to keep them disabled by default.

stek29 on 6 Dec 2016

Yeah, I agree

Marocco2 on 6 Dec 2016

anyone know when this will be pushed to non insider? still problem on 1607