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

rocketchat-desktop version 3.2.2 crashes on Ubuntu 20.04 when disabling GPU acceleration. #2045

Closed
ssether-usinternet opened this issue May 17, 2021 · 3 comments · Fixed by #2318

Comments

@ssether-usinternet
Copy link

When I tried disabling GPU acceleration, the client immediately crashed. When i started it with the CLI, it didn't provide any debug information on crashing. I'm on Ubuntu 20.04.2 LTS, and have updated all packages as of today 5/17/2021.

I previously un-installed, and re-installed rocketchat-desktop to 3.2.2 via snap to solve a different problem where the client crashed immediately, so it doesn't appear to be a stale config issue.

I don't really need to disable GPU acceleration, so this isn't critical. But maybe this is an issue for others.

@johncrisp
Copy link

This is against the Electron client.

Can you please fill ii a proper bug report template with al the Rocket.Chat server info? At a guess is a snap it is 3.13.2 but we need to know.

Moving this to the Electron repo.

@johncrisp johncrisp transferred this issue from RocketChat/Rocket.Chat May 17, 2021
@ssether-usinternet
Copy link
Author

ssether-usinternet commented May 17, 2021

Operating System / Version / Architecture (64 bit?)
Ubuntu 20.04.2, 64 bit.

Browser type and version, including any add-ons. (e.g., AdBlocker, NoScript, etc.)
N/A? I'm running the client.

Rocket.Chat version
3.2.2

Expected behavior
Turn off GPU acceleration

Actual behavior
Hard crash.

Can the bug consistently be reproduced? If so, how?
Yes, every time. Just go to file, disable CPU and it immediately crashes.

Relevant errors and other log output
No errors I can see, none produced when I launch the program from the CLI.

Server version: 3.14.0 (doesn't appear relevant, crashes even if I don't connect to the server, and even after I remove the server info entirely).

@obff
Copy link

obff commented Oct 13, 2021

Hello there,

same here for

Rocket.Chat version
3.5.7

Operating System / Version / Architecture (64 bit?)
ArchLinux 5.14.11-arch1-1

After starting the program I get
[7692:1013/221516.678614:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. on stdout.

After clicking the Diasable GPU button the client GUI just crashes without any further output to stdout or stderr.
But some background processes and threads are still alive.

Starting the client again still outputs [7692:1013/221516.678614:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. on stdout.
But no further processes nor the GUI are started nor seem the old processes to be affected.

I first have to kill the old processes.
After doing so I can start the client including the GUI again. Clicking Disable GPU starts everything from the beginning.

This are the processes that survived the GUI crash and have to manually killed:

$ ps  -o arg
...
/usr/lib/electron/electron --disable-gpu /usr/lib/rocketchat-desktop
/usr/lib/electron/electron --type=zygote --no-zygote-sandbox
/usr/lib/electron/electron --type=zygote
/usr/lib/electron/electron --type=zygote
/usr/lib/electron/electron --type=gpu-process --field-trial-handle=4763844154967642569,4666904126412529815,131072 --disable-features=SpareRendererForSitePerProcess --user-data-dir=/home/*******/.config/Rocket.Chat --gpu-preferences=UAAAAAAAAAAgAAAIAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAAAAAAAAGAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --use-gl=swiftshader-webgl --shared-files
/usr/lib/electron/electron --type=broker
...

Cheers,
Robert

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

Successfully merging a pull request may close this issue.

3 participants