Git Product home page Git Product logo

Comments (6)

scottnonnenberg-signal avatar scottnonnenberg-signal commented on June 1, 2024 1

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

trevor-signal avatar trevor-signal commented on June 1, 2024

@avi12 is this reproducible for you?

from signal-desktop.

avi12 avatar avi12 commented on June 1, 2024

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

from signal-desktop.

davidfraser avatar davidfraser commented on June 1, 2024

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.

scottnonnenberg-signal avatar scottnonnenberg-signal commented on June 1, 2024

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

davidfraser avatar davidfraser commented on June 1, 2024

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.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.