Desktop app hung/slow performance

[jeremymasters]

• [x] I have searched open and closed issues for duplicates

Bug description

was using signal desktop and this morning it seems to be laggy and it even hung and went white-screen on me.

Steps to reproduce

1. using signal desktop
2. messaging people
3. get group message

Actual result:

signal desktop hangs or is laggy

Expected result:

smooth operator

Signal version:
1.17.0

Operating System:
Win10 Pro

Linked device version:
Android 8.0 stock, Signal 4.29.5

Link to debug log

https://debuglogs.org/17062bfbcd97e2a1b956a5ee69727e76f7eeb5057eacd7fae0e862130c5e413b

[scottnonnenberg-signal]

@jeremymasters At about what time did this happen? Also, is there any additional information you can provide about what was happening, what you were trying to do when things went wrong? I see one really long session ending right near the end of the log, and a pretty short session at the end there - but nothing obvious. Anything else you can provide would be helpful.

[jeremymasters]

I captured that log a couple minutes after the white screen of the app. Couldn't tell you what time of day, but it wasn't too far away from the end of that log. I wasn't really using it in any different way than I have for quite some time, which is why it struck me as odd. I'll update this further if I think of anything else.

[deutrino]

I'm experiencing occasional small freezes of 1-10 seconds on desktop on Linux (Ubuntu 18.04), with a SSD. My friend with whom I chat the most on Signal (hundreds of messages per day) is getting ones that last a lot longer on a HDD. It seems that freezes may be related to heavy disk activity (but not always). Occasionally painting of some of the UI components gets weird. Often if you are typing, whatever you typed during the freeze will be eaten. This started within the last month or two.

[vbspam]

I suffer the same symptoms. Ubuntu 18.04, most recent Signal-desktop app. The pity is that one can not use previous non-buggy versions :-(.

[scottnonnenberg-signal]

This is our central startup performance issue: #3010