Unhandled Promise Rejection

[avi12]

Using a supported version?

• [X] I have searched searched open and closed issues for duplicates.
• [X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Clicked X multiple times to close, then crashed with an error every time I tried to open

Steps to reproduce

1. I had a chat open
2. Pasted a screenshot
3. Added an emoji
4. Pressed enter, but noticed that it added a new line rather than sending it
5. Tried to close the app, but the window didn't close, so I pressed multiple times the close button
6. I tried to reopen the app, but got the error I posted in "Actual result"

Expected result

Normally it closes and opens up as usual I fixed the issue by terminating Signal's process and relaunching the app

Actual result

Unhandled Promise Rejection

Error: EPERM: operation not permitted, unlink 'C:\Users\avi12\AppData\Roaming\Signal\logs\app.log.3'

Screenshots

No response

Signal version

7.8.0

Operating system

Windows 10 22H2

Version of Signal on your phone

No response

Link to debug log

https://debuglogs.org/desktop/7.8.0/92c8fb86235165a19932f9764515ebe0461b6cfcb0ac3b8946374a1363efca8b.gz

[trevor-signal]

@avi12 is this reproducible for you?

[avi12]

Sadly no, ever since I terminated Signal's process and relaunched it, it's not reproducible

[davidfraser]

I had a similar issue - the same error message, but with app.log instead of app.log.3. I couldn't see any information about app.log using icacls or takeown. I used File Locksmith from PowerToys (as recommended here) to see what had locked something in the logs directory. It found that there was a signal.exe still running, though there was no sign of it. I terminated that and Signal was able to start fine again...

[scottnonnenberg-signal]

@davidfraser We'd love to see debug logs for the situation you've described. It seems like Signal Desktop is taking too long to shut down, and also not properly detecting a second instance before starting up!

[davidfraser]

OK, this only happened once yesterday - here are the logs I can get, but it seems they only include the new session, not the dead one: https://debuglogs.org/desktop/7.10.0/e08e4d3bf90f6d897ca438498dfcb1b629edddc66fa26163b18c6f52cfa870e1.gz

[scottnonnenberg-signal]

@davidfraser Thanks for the debug log - it looks like you did have a crash or somehow ungraceful exit. But we don't have any information about it. If you start using the app with the --enable-crash-reports command-line argument, your future debug logs will include crash information.

WARN  2024-05-28T11:31:11.458Z cancelInflightRequests/powerMonitorSuspend: Cancelling 0 requests
WARN  2024-05-28T11:31:11.458Z cancelInflightRequests/powerMonitorSuspend: Done
INFO  2024-05-28T11:31:11.458Z TaskWithTimeout: suspending 0 tasks
INFO  2024-05-28T11:31:11.458Z powerMonitor: suspend
WARN  2024-05-28T11:31:11.458Z cancelInflightRequests/powerMonitorSuspend: Cancelling 0 requests
WARN  2024-05-28T11:31:11.458Z cancelInflightRequests/powerMonitorSuspend: Done
INFO  2024-05-28T11:31:11.458Z TaskWithTimeout: suspending 0 tasks
<crash here? no quit events>
INFO  2024-05-28T13:07:50.422Z got fast localeOverride setting null
... startup stuff
INFO  2024-05-28T13:07:50.492Z app ready

[davidfraser]

I turned on debug logging, and then got told that there was a crash - logs here although I don't think this was the same event https://debuglogs.org/desktop/7.11.0/921bbf7aaf3a53bb483154d6da0d1311285da4ff72ec971ee1ba00f76dd07bdb.gz

[jamiebuilds-signal]

@davidfraser looks like thats a different issue with EXCEPTION_BREAKPOINT, it looks like this happened soon after a network connection was reset. Did you make any changes to your network before this happened? Such as changing wifi networks or turning a VPN on/off?

WARN  2024-06-01T01:01:27.750Z WebSocketResource(authenticated): WebSocket error Error: read ECONNRESET

[davidfraser]

Hmmm, I didn't switch networks at that point. So I'm not sure. But will upload another debug log if I get into the same situation as reported in this bug originally

[avi12]

A friend messaged me on Signal, I got a notification on mobile, and then I switched to the desktop app but noticed that it wasn't synchronized for some reason I tried to close the desktop app, didn't respond the first time so I clicked X a second time and a moment later I got app.log

I tried to reopen Signal on the desktop, got the error again I suspect that similar to my original post, the only way to work around it is by terminating the Signal process

[indutny-signal]

@avi12 sadly, this is very likely true. If you'll attempt to terminate it - could you make note which processes were running? So far we lack this information and it is hard to take action on the issue.

[ghost-ng]

I just got the same error. I can't open the log though - it seems there is still a handle to it (notepadd++ says it can't find it and wants to create it). Also the process is still open in the tasklist. Issue started with some weird GUI issues where the channels wouldn't change when I would select them.

After killing the background process the log disappeared (maybe stop doing that lol). Once I reopened signal everything worked. I have windows 11 is that makes a difference.

[indutny-signal]

@ghost-ng I see. Sorry about this. There is probably still a Signal process that remains in the task manager and keeps the handle to the file. At this point, the simplest fix might be to restart your computer. Sorry this happened!