-
Notifications
You must be signed in to change notification settings - Fork 43
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
SIGTRAP on Manjaro Linux #165
Comments
It is hard to tell the reason without some more details, can you run in a debugger or examine the core dump to see where the crash happens? For reference: |
I'll do that once I'm back at my laptop. |
Hello, I have this bug too. After futher investigation, I noticed that your electron will not work when launching it on an other Electron app (like Visual Studio Code) on the lastest Ubuntu (22.04.3 LTS), because, when I do
On v26.0.0 and more, I have a new error with SIGTRAP :
When I use gdb, I have this :
When I launch ./node_modules/electron/dist/electron in the VSCode's terminal, I have 3 core dump.
Here are these core dump, but they showing anything to help...
I did the same test with Electron not modified, I can launch electron in VSCode. I can launch your Electron in VSCode only if I put theses args : --no-sandbox --disable-gpu-sandbox, but I have a white screen because the GPU is disabled. If I remove one of these arg, app will not work. How to repro the bug:
Note: sorry for my bad English. |
Oh, sorry, I very much forgot that I opened this issue. This happens when I use gdb:
I can confirm that it runs for me as well with |
This seems to be some kind of problem related to the zygote process (a process that launches other processes), at least that is what the failing check above is about. Can you try with the arguments |
It works with |
I can confirm that it works with |
The electron binary exits with SIGTRAP when starting on Manjaro Linux.
The dependency I added for electron is:
https://github.com/castlabs/electron-releases#v25.4.0+wvcus
This is everything that logs:
The text was updated successfully, but these errors were encountered: