Disable the Zygote process to prevent it from randomly crashing#334
Disable the Zygote process to prevent it from randomly crashing#334guihkx wants to merge 1 commit intoflathub:masterfrom
Conversation
This launches Spotify with --no-zygote by default, in order to prevent the Zygote process from randomly crashing and generating useless coredumps. This problem is not exclusive to the Flatpak package. See: - https://community.spotify.com/t5/Desktop-Linux/Spotify-binary-frequently-crashing-and-dumping-core-Ubuntu/td-p/6534369 Fixes flathub#320
|
🚧 Test build enqueued. |
|
🚧 Started test build. |
|
✅ Test build succeeded. To test this build, install it from the testing repository: |
|
@Erick555, @TingPing: FWIW, I've been using this option for ages in my |
|
According to docs zygote is used for memory optimization and sandboxing. AFAIK spotify uses --no-sandbox right now so the latter may be not a problem right now but it may change in the future. I'm not sure if we should force this fix for a minor issue if users can workaround it quite easily if it bothers them. |
|
The memory optimization part makes sense and is valid, but I have my doubts about the importance of the sandbox in this context, given that Flatpak already provides one... Electron apps, for example, have been using zypak for ages to essentially disable the built-in Chromium sandbox to avoid issues when running them through Flatpak. I just personally dislike having my disk constantly sprayed with useless coredumps that contribute to SSD wear, and it's likely that the average user doesn't even know this is happening in the background when they leave Spotify running for hours. In any case, it's fine if you don't think this is worth merging, so feel free to close this. |
3 participants
This launches Spotify with
--no-zygoteby default, in order to prevent the Zygote process from randomly crashing and generating useless coredumps.This problem is not exclusive to the Flatpak package. See:
Fixes #320