Skip to content
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

Render process is gone #7100

Open
2 tasks done
kornelshakh opened this issue Nov 25, 2024 · 20 comments
Open
2 tasks done

Render process is gone #7100

kornelshakh opened this issue Nov 25, 2024 · 20 comments
Labels

Comments

@kornelshakh
Copy link

Using a supported version?

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

Overall summary

This is happening to me since the last few Signal updates.

If I uninstall Signal and install it again, it will work for as long as I don't close Signal/turn off PC.

If I use Signal on phone while it's not running on desktop it will cause this crash loop eventually.

The same issue is on all my desktop devices that have Signal installed, same for my friends.

Crash log:
Error: Reason: crashed, Exit Code: 134
at App. ([REDACTED]\app\global_errors.js:94:7)
at App.emit (node:events:519:28)
at WebContents. (node:electron/js2c/browser_init:2:87687)
at WebContents.emit (node:events:519:28)

App Version: 7.33.0
OS: win32

Steps to reproduce

  1. Open Signal

Expected result

Should load Signal and not crash.

Actual result

Will show the loading screen for few minutes, then freeze, and then after some time crash.

Screenshots

No response

Signal version

7.33.0

Operating system

Windows 11

Version of Signal on your phone

No response

Link to debug log

No response

@trevor-signal
Copy link
Contributor

Hi @kornelshakh, sorry this is happening! A debug log after this crash happens would be super helpful to diagnose what's going on. Can you compress your logs folder (at C:\Users\<YourName>\AppData\Roaming\Signal\logs) and share it with us? If you'd prefer not to attach it to this issue, you can email it to [email protected] and reference GH issue #7100. Thanks!

@kornelshakh
Copy link
Author

Hello @trevor-signal, here is the compressed logs.zip folder. I would appreciate if you could look into this issue, this has caused major inconvenience for my day-to-day life, thank you!

@jamiebuilds-signal
Copy link
Member

It looks like you have a lot (like over a million) pending tasks in your database that are likely processing delivery receipts, and we're running out of memory trying to load them all.

We can and should stop loading them all at once, and we might need to be more aggressive about deleting them, hopefully we can get you a fix soon.

@jamiebuilds-signal
Copy link
Member

@kornelshakh I don't know for certain, but just something to try in case it gets things working for you again. If you keep restarting the app for a total of 5+ times, it may clear out all of the old tasks that's causing your crashes.

(We only attempt to run these tasks 5 times before we delete them, so I'm hoping you can force them to get deleted)

@kornelshakh
Copy link
Author

@jamiebuilds-signal Hello, the crash is still happening even after 5+ restarts. Nothing works other than reinstalling it completely which is hassle to do every time I want to use the app. Hopefully there will be a solution for this, thank you.

@rex4539
Copy link
Contributor

rex4539 commented Jan 26, 2025

I got this as well a couple of times with the latest beta build.

Render process is gone

Error: Reason: crashed, Exit Code: 6
    at App.<anonymous> ([REDACTED]/app/global_errors.js:94:7)
    at App.emit (node:events:518:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:87957)
    at WebContents.emit (node:events:518:28)

App Version: 7.40.0-beta.2
OS: darwin

https://debuglogs.org/desktop/7.40.0-beta.2/252d83db20d67aa941a72f780e2101d783251471a346cc9ea2aea196d65e555b.gz

@rex4539
Copy link
Contributor

rex4539 commented Jan 27, 2025

Again.

Render process is gone

Error: Reason: crashed, Exit Code: 6
    at App.<anonymous> ([REDACTED]/app/global_errors.js:94:7)
    at App.emit (node:events:518:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:87957)
    at WebContents.emit (node:events:518:28)

App Version: 7.40.0-beta.2
OS: darwin

https://debuglogs.org/desktop/7.40.0-beta.2/a3252713aa9b3ee158078b4be084fb6647980bdd4cee7867a08be0b62c99fb88.gz

@rex4539
Copy link
Contributor

rex4539 commented Jan 28, 2025

Once more.

Render process is gone

Error: Reason: crashed, Exit Code: 6
    at App.<anonymous> ([REDACTED]/app/global_errors.js:94:7)
    at App.emit (node:events:518:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:87957)
    at WebContents.emit (node:events:518:28)

App Version: 7.40.0-beta.2
OS: darwin

https://debuglogs.org/desktop/7.40.0-beta.2/223679af08001a29bbdd352633cb10a4573d589cf7259817e306fd1b9e692a7e.gz

@rex4539
Copy link
Contributor

rex4539 commented Jan 28, 2025

Again.

Render process is gone

Error: Reason: crashed, Exit Code: 6
    at App.<anonymous> ([REDACTED]/app/global_errors.js:94:7)
    at App.emit (node:events:518:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:87957)
    at WebContents.emit (node:events:518:28)

App Version: 7.40.0-beta.2
OS: darwin

https://debuglogs.org/desktop/7.40.0-beta.2/8382331afa6c89080fe5ae4e8c28dada613ee2ad4aee05288670311aa7d5b28f.gz

@rex4539
Copy link
Contributor

rex4539 commented Jan 29, 2025

With the new build.

Render process is gone

Error: Reason: crashed, Exit Code: 6
    at App.<anonymous> ([REDACTED]/app/global_errors.js:94:7)
    at App.emit (node:events:518:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:87957)
    at WebContents.emit (node:events:518:28)

App Version: 7.41.0-beta.1
OS: darwin

https://debuglogs.org/desktop/7.41.0-beta.1/5ee44a92c10bccb3068a455c7b6740310e46972ef1977ba00262772f381e4f95.gz

@rex4539
Copy link
Contributor

rex4539 commented Jan 30, 2025

I have found a surprising(!) way to reproduce 100%.

Prerequisites:
Pair AirPods with your computer. I'm using AirPods 4 on a MacBookPro15,1.

Steps:

  1. Open Signal Desktop and select a chat from the chat list.
  2. Open your AirPods case and put both earphones in your ears.
  3. Close your AirPods case and wait for 3 seconds.
  4. Open your AirPods case and put both earphones back in the case.

What happened:
As soon as the 2nd earphone is placed back in the case (no need to close the case), Signal Desktop crashes.

Notes:
According to this scenario, it looks like the crash is caused by some bug in the logic of audio device switching. Because as soon as the 2nd earphone is placed back in the case, the AirPods are disconnected from the computer.

@yash-signal
Copy link
Contributor

Thank you for the report @rex4539 . Can you open a separate GitHub issue for this?

@rex4539
Copy link
Contributor

rex4539 commented Jan 30, 2025

Perhaps it was not clear from the report.

These are the steps to reproduce the bug reported in this thread.

So opening a new report would just be a duplicate.

@mutexlox-signal
Copy link
Contributor

@rex4539 thanks so much for the report! Very much appreciated.

Can you please confirm whether the AirPods disconnect altogether from the computer, or whether the connection is still there but they're no longer the selected system default in System Settings > Sound?

@rex4539
Copy link
Contributor

rex4539 commented Jan 30, 2025

They disconnect altogether from the computer.

@mutexlox-signal
Copy link
Contributor

@rex4539 I'm having trouble reproducing the crash, as are my colleagues, though hopefully it will no longer happen for you (possibly after restarting the app once).

If you're comfortable posting here, can you please share what other audio devices you have connected, both for mics and speakers/headphones? If you'd rather not share that publicly feel free to email me directly, too. (My email is my github username minus the "-signal" at signal dot org.)

@rex4539
Copy link
Contributor

rex4539 commented Jan 31, 2025

No other devices, except the built-in.

@mutexlox-signal
Copy link
Contributor

Does Signal's preferences pane for calls show any unexpected microphones or speakers? I expect probably not at this point, but it could be worth checking.

@mutexlox-signal
Copy link
Contributor

@rex4539 Unfortunately we're still having difficulty reproducing, but I want to get to the bottom of this issue, so could you please run the following steps?

  1. View > Toggle Developer Tools
  2. In the console that pops up, run SignalDebug.setUseRingrtcAdm(true);
  3. Exit Signal
  4. From a terminal, run /Applications/Signal\ Beta.app/Contents/MacOS/Signal\ Beta (substituting the path to Signal Beta on your machine, as appropriate)
  5. Reproduce the crash
  6. Copy/paste the logs from the Terminal. Either email these to me directly or post as a comment here, up to you.
  7. Open Signal Beta as usual
  8. View > Toggle Developer Tools
  9. Run SignalDebug.removeUseRingrtcAdm();
  10. Restart Signal Beta as usual

@rex4539
Copy link
Contributor

rex4539 commented Feb 1, 2025

Well, after multiple OS restarts, I don't get the bug anymore.

But in case my computer reaches a state where I can reproduce it again, I will try the steps above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

6 participants