search

sharpie7 / circuitjs1

Electronic Circuit Simulator in the Browser
GNU General Public License v2.0
2.35k stars 642 forks source link

GPU process isn't usable. Goodbye. #768

Open mabret opened 2 years ago

mabret commented 2 years ago

When I try to run circuitjs1, a window appears briefly then disappears. The program says:

8057:0509/223206.357874:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

It exits with code 133.

inxi gives the following output:

CPU: quad core Intel Core i7-3770 (-MT MCP-)
speed/min/max: 1741/1600/3900 MHz Kernel: 5.15.0-27-lowlatency x86_64 Up: 42m
Mem: 2382.3/32060.7 MiB (7.4%) Storage: 2.05 TiB (23.1% used) Procs: 287
Shell: Bash inxi: 3.3.13

Nvidia GT1030, driver version 470.103.01

The same error occurs with driver version 510

ormaaj commented 2 years ago

What leads you to think this is related to circuitjs? Did you build this to run under electron? This problem could originate almost anywhere but circuitjs - the browser, any library it's linked against, the Nvidia driver, any part of the graphics stack - we can't know without a backtrace, system logs, and possibly other tracing depending on where the issue is.

It exits with code 133

The max exit status is 127.

bash(1) says:

The return value of a simple command is its exit status, or 128+n if the command is terminated by signal n.

Use kill -l to print the signal list.

signal(7) says:

There are six signals that can be delivered as a consequence of a hardware exception: SIGBUS, SIGEMT, SIGFPE, SIGILL, SIGSEGV, and SIGTRAP. Which of these signals is delivered, for any given hardware exception, is not documented and does not always make sense.

That's the only clue. Your video card could be dying.

A crash course on how to get the needed info is here , but you'll have to report the issue to the appropriate maintainers since the problem will be unrelated to this project.

pfalstad commented 2 years ago

It seems to be an electron bug which has since been fixed. You could try using --no-sandbox or --disable-gpu-sandbox, or download a newer version of electron and run it in the same directory as circuitjs1 (circuitjs1 is just an electron binary that's been renamed). I don't have linux so I can't try it.

thiago1255 commented 1 year ago

It seems to be an electron bug which has since been fixed. You could try using --no-sandbox or --disable-gpu-sandbox, or download a newer version of electron and run it in the same directory as circuitjs1 (circuitjs1 is just an electron binary that's been renamed). I don't have linux so I can't try it.

I had the same problem, run with "--disable-gpu-sandbox" works ! thx