Catsxp 3.3.5 beta 1 W7 64 bit

[Jeffhere]

"Win7: You need to add the startup parameter -- no sandbox to start normally (GPU process launch failed: error_code=2). After several days of checking, the cause of the problem was not found!"

When I enter the -- no sandbox parameter as instructed, Catsxp immediately crashes with no error message at all.

I removed the space between the 2 dashes and the first letter of the parameter, since all other default parameters have no space between the dashes and text like such

--no sandbox

Then I tried adding a dash between no and sandbox, since all the default parameters use a dash in between words, no spaces.

--no-sandbox

Now 3.3.5 beta 1 runs but prompts me the following info:

Capture.GIF (7.1 KiB) 查看 2341 次

I am removing 3.3.5 beta 1 until further instruction is provided. Thanks for all your work!

[catsxp]

--no-sandbox

[Jeffhere]

yes, that was one I tried that allowed catsxp to run but with the warning, as you can see in the pic

I used an updated list (I assumed catsxp is based on chromium) at https://peter.sh/experiments/chromium-c ... -switches/

[s6nonqxt9y886fdp]

It's not recommended to use Chromium with --no-sandbox flag. People said Google themselves recommend using another browser than using Chrome without sandbox.

https://unix.stackexchange.com/question ... ndbox-mean

[catsxp]

try beta-3
If there is an abnormal crash, please send the dump file to my mail

[catsxp]

It's not recommended to use Chromium with --no-sandbox flag. People said Google themselves recommend using another browser than using Chrome without sandbox.

https://unix.stackexchange.com/question ... ndbox-mean

I know, but I can't confirm whether it's due to a sandbox code issue or other code that caused the sandbox exception! The Google kernel code has changed too quickly to know exactly what code they have changed causing these problems