-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled Promise Rejection #6877
Comments
@avi12 is this reproducible for you? |
Sadly no, ever since I terminated Signal's process and relaunched it, it's not reproducible |
I had a similar issue - the same error message, but with |
@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! |
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 |
@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
|
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 |
@davidfraser looks like thats a different issue with
|
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 |
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 reopen Signal on the desktop, got the error again |
@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. |
Using a supported version?
Overall summary
Clicked X multiple times to close, then crashed with an error every time I tried to open
Steps to reproduce
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
The text was updated successfully, but these errors were encountered: