Unhandled Promise Rejection about signal-desktop HOT 11 OPEN

@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

from signal-desktop.

@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.

from signal-desktop.

@avi12 is this reproducible for you?

from signal-desktop.

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

from signal-desktop.

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...

from signal-desktop.

@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!

from signal-desktop.

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

from signal-desktop.

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

from signal-desktop.

@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

from signal-desktop.

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

from signal-desktop.

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

from signal-desktop.