MacOS Sonoma Crash - Render process is gone

[Synesso]

• I have searched open and closed issues for duplicates

• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

---

Bug Description

Since updating to MacOS Sonoma 14.0, Signal will crash. It happens at a time not associated with my using it. After crashing once or twice, it is automatically removed from Applications and I need to reinstall & relink it.

The error is

Render process is gone

Error: Reason: killed, Exit Code: 15
    at App.<anonymous> ([REDACTED]/app/global_errors.js:88:7)
    at App.emit (node:events:525:35)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:90123)
    at WebContents.emit (node:events:513:28)

Steps to Reproduce

1. install signal
2. link device (this may be optional)
3. wait appx 30 minutes.

Actual Result:

Abrupt crash

Expected Result:

No crash.

Platform Info

Signal Version:

v6.31.0

Operating System:

MacOS Sonoma v14.0
M1 Max

Linked Device Version:

iOS v6.42.0.18

Link to Debug Log

Unable to locate the debug view as the application is removed immediately after crash.

ooooh, I wonder if the os is removing the application and that's why it crashes?

[indutny-signal]

Sorry about this. Could you try running Signal Beta to see if it works, please? https://support.signal.org/hc/en-us/articles/360007318471-Signal-Beta

[khepin]

I'm having the same thing, tried the beta version and Signal just crashed again with the same error. Let me know how I can help provide more info.

[JodyVanden]

Yes I am having the same issue. Here are my logs
https://debuglogs.org/desktop/6.34.0-beta.2/5a3531c3f0746f1b5bdac1f66a38600708a0d61b3fceb20a9a83f24798786e4e.gz

With the normal version of signal the app is removed from the application folder when the error happens
With the beta version the error still remains but the app is not removed (which is already an improvement)
more info on this duplicated bug

[indutny-signal]

@JodyVanden next time it crashes - could you submit the crash dump and send it to us? It should ask you to submit it on startup after the crash. Thanks!

[khepin]

I don't get asked to submit a report after restarting the app when a crash has occurred.

[JodyVanden]

hey, @indutny-signal I don't get asked to submit a crash dump report. that's why I submitted all the logs. I will keep an eye for the next crash and can resubmit logs if that is useful?

[Synesso]

Happened again just now. Beta version. App was running for about 30 minutes.

This is the dialog

Restarted and saved logs: https://debuglogs.org/desktop/6.34.0-beta.2/519a3a2f1ac42768dac99ea1ffbca8c66339a77448f23b25531d9d327b04a8f4.gz

[awaitlink]

Also got a crash, it happened specifically when first trying to connect to Windscribe VPN while no Signal Desktop windows were shown (but it was running), not sure if that's related though.

https://debuglogs.org/desktop/6.38.0-beta.1/desktop-crash-870b28b4594daee25f5742803441afeb7d96dae7998d301d8e8dae4c0fb65713.dmp

https://debuglogs.org/desktop/6.38.0-beta.1/3285b69a0b4e7066f37b26375b27c4a565e15fbb6a4e06c75d2420d4c409c4f6.gz

Render process is gone
Error: Reason: crashed, Exit Code: 11
    at App.<anonymous> ([REDACTED]/app/global_errors.js:88:7)
    at App.emit (node:events:525:35)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:90245)
    at WebContents.emit (node:events:525:35)

[HenningWaack]

Happens on my mac, too, and I strongly suspect that it happens whenever I connect or disconnect from a VPN.

[scottnonnenberg-signal]

Yes, it does seem to be related to this: #6496

Different exit code, though!

[Synesso]

I tested again without enabling VPN and it crashed in the same manner. VPN is installed though, just wasn't active.

…

On Wed, 15 Nov 2023 at 03:25, Scott Nonnenberg ***@***.***> wrote: Yes, it does seem to be related to this: #6496 <#6496> Different exit code, though! — Reply to this email directly, view it on GitHub <#6622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFKY4CILVCTX4HYRJOII3YEOSQJAVCNFSM6AAAAAA5MAFXFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQG42TCOJYGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>