[Pretty Minor] Issue with electron apps when running with proxychains4

Config and other information has not changed since my last issue post which is here: https://github.com/rofl0r/proxychains-ng/issues/585

I will add new config and other edits if needed in the future.

Not sure if it is either electrum or proxychains related issue. When running an app that uses electrum like discord, signal etc you will be required to add --no-sandbox --in-process-gpu at the end of the target if you want to route its traffic through proxychains and have it boot successfully.
If you do not parse the workaround above then the process will just throw an error and exit which is supplied at the bottom and in the screenshot below

Although this work around does not always work with some applications like discord as I had to flatpak install it for it to work compared to the debian install.

I will provide a screenshot below to help show the issue:

The second time I had run signal with proxychains and also parsing the workaround mentioned above is a successful start and run. The above is pretty obvious.

Console output in event of error:

┌─╼[~]
 └╼ ❯❯❯ proxychains4 signal-desktop                              
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[12627:1113/182953.017777:FATAL:zygote_host_impl_linux.cc(221)] Check failed: . : Invalid argument (22)
[1]    12627 trace trap  proxychains4 signal-desktop

No source file or test is identified. Start by reproducing the reported command, proxychains4 signal-desktop, with and without --no-sandbox --in-process-gpu, then inspect the proxychains-ng startup path and the reported Electron zygote error. Done means determining whether the failure is in proxychains-ng or the Electron application and documenting a reproducible resolution.