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

[indutny-signal]

@Synesso could you try reproducing it with Signal Beta and send us a crash dump, please? Thanks!

[Synesso]

This was beta. Sorry, there is still no crash dump. I suspect, at least in my case, it *may* be Malwarebytes or something similar nuking the process as a "security" measure.

…

On Wed, 15 Nov 2023 at 08:04, Fedor Indutny ***@***.***> wrote: @Synesso <https://github.com/Synesso> could you try reproducing it with Signal Beta and send us a crash dump, please? Thanks! — Reply to this email directly, view it on GitHub <#6622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFKYZICQ2G2WD73RNZ6A3YEPTGPAVCNFSM6AAAAAA5MAFXFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRGQZTKMRXHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[indutny-signal]

@Synesso ah, right. This is indeed not related. Absence of crash dump is a sign that the process likely didn't actually crash at all and was killed.

[dgobaud]

just happened to me but on OSX Monterey 12.3 (21E230). no vpn.

first time ever. i had just pasted a message with a link into a chat and it was generating the preview then crashed

https://debuglogs.org/desktop/6.42.1/8cb55962d207f1204889ed318a1729f49165f1dabbc2061084044cf4030d3395.gz

Signal - 6.42.1

Error: Reason: crashed, Exit Code: 5
    at App.<anonymous> ([REDACTED]/app/global_errors.js:88:7)
    at App.emit (node:events:526:35)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:89748)
    at WebContents.emit (node:events:526:35)

[ayumi-signal]

@dgobaud Sorry this is happening for you. I took a look at the logs and can't find anything obviously wrong.

Can you reproduce the crash regularly; and is it possible to try the Beta build so crash dumps would be available for us to look through? https://support.signal.org/hc/en-us/articles/360007318471-Signal-Beta

[dgobaud]

Thanks for looking it only happened once so far

…

On Wed, Jan 3, 2024 at 10:34 PM ayumi-signal ***@***.***> wrote: @dgobaud <https://github.com/dgobaud> Sorry this is happening for you. I took a look at the logs and can't find anything obviously wrong. Can you reproduce the crash regularly; and is it possible to try the Beta build so crash dumps would be available for us to look through? https://support.signal.org/hc/en-us/articles/360007318471-Signal-Beta — Reply to this email directly, view it on GitHub <#6622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB2ZK63JYW72NLI7UXEAK3YMYPM7AVCNFSM6AAAAAA5MAFXFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGI3DENBQGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[khepin]

This time I was able to get the following error message:

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:526:35)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:89748)
    at WebContents.emit (node:events:526:35)

This is on Signal Beta. Hope this helps.

[scottnonnenberg-signal]

@khepin The exit code is something, but the crash dump (you should see a prompt when you next start up after a crash) is what we really need.

[khepin]

Still not getting those unfortunately

[scottnonnenberg-signal]

@khepin Have you tracked it down to anything you're doing in the app, or is happening on your computer? (like a VPN change or other network change, say)

[khepin]

Nope, I thought it was VPN earlier on, but it's clearly not related.

[cmahnke]

Nope, I thought it was VPN earlier on, but it's clearly not related.

Well, actually for me it is, on the Network Change event (trigged by initiating a VPN Connection), I get:

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

This is on Signal Desktop Version 6.44.0 (1) on Sonoma 14.2.1 (23C71)

[rjanalik]

Hello,
I am observing pretty much the same problem, but crashing with Exit Code: 10.
It crashes every time Cisco Secure Connect connects. The native VPN client was not causing this issue.
M2 MacBook Pro, Sonoma 14.2.1

[rjanalik]

Here is the log
https://debuglogs.org/desktop/7.5.0/a08b7700ee65a0cb747c5469d274d922955ef04dff0d05d1dfc1465563b09b1e.gz

[scottnonnenberg-signal]

It's possible that this new option may help you avoid crashes? bcaf60a

[rjanalik]

It seems it still crashes with --disable-ipv6
Here is the log https://debuglogs.org/desktop/7.5.0/fe51dd4e9f683c6d3464b2133ea4df05f2face02894712b2eecbc657517f7037.gz

I have Signal version 7.5.0. I am not able to say if this version already has --disable-ipv6 or not, though.

[indutny-signal]

@rjanalik sorry, it actually doesn't have it yet. Could you try installing a beta? Thank you!

[rjanalik]

Sure. Can I install it side by side with the stable version?

[indutny-signal]

@rjanalik yup, they will be completely isolated from each other. Thank you!

[rjanalik]

I just tried 7.6.0-beta3, started it like this

$ /Applications/Signal\ Beta.app/Contents/MacOS/Signal\ Beta --disable-ipv6

and it keeps crashing when I connect to VPN.

[indutny-signal]

@rjanalik could you send a debug log, please?

[rjanalik]

https://debuglogs.org/desktop/7.6.0-beta.3/b87dc9699b602825aa79a7d928da7eadabc48f8dc4e09b6e9fd2d4b2e83a5148.gz

[indutny-signal]

Ah, I see. Sorry about this, I don't think --disable-ipv6 is working to full extent in this release either yet. Next prod and beta release (coming this week) should have it available! Thank you for your patience!

[rjanalik]

No problem. Please, let me know if there is something else to help.

[cmahnke]

See also https://debuglogs.org/desktop/7.5.1/3721ae1bf0c0f8de28c4f20ff697e2d78e45654d7ba42875e5c7b4039c6b15e8.gz

[rjanalik]

I have been using version 7.7.0 for a few days and it seems --disable-ipv6 solves the issue. Thanks!

[rjanalik]

Are there any plans to have this option also in the GUI settings?

[ckujau]

Still happens on macOS 14.6.1 (M3 Pro) and Signal 7.21.0-beta.2:

https://debuglogs.org/desktop/7.21.0-beta.2/c747d66ca1cdd92a7309b09b25d4997ed0ab5cc24644ec18a78d8a4e3cbbd367.gz

Render process is gone

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

[jeanas]

I am getting roughly the same error on a regular basis:

Render process is gone

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

App Version: 7.24.1
OS: linux

This is with the Flatpak version of Signal on Fedora 40 (with Wayland).

[indutny-signal]

@jeanas sorry, but the crash you reported is likely a separate issue. Furthermore, flatpak is not an officially supported distribution. I'd suggest reaching out to the maintainers of your package.

[hurani]

Render process is gone

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

App Version: 7.36.1
OS: darwin

Just got this same crash with Signal chilling in the background, wasn't touching it for a while. Googled the error and it took me to this thread.

[drdaz]

Render process is gone

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

App Version: 7.36.1
OS: darwin

Just got this same crash with Signal chilling in the background, wasn't touching it for a while. Googled the error and it took me to this thread.

I'm seeing the same thing. Interestingly, I'm only seeing this on my new M4 Mac mini. I've got several other desktop installs on macOS (both Intel and AS), and none of them fail like this. I figured it was related to the new CPU... but I guess not.