Linux Desktop app crashes trying to allocate GPU resources

sgh · November 28, 2022, 2:57am

Steps to reproduce

Start a Kubuntu LTS desktop (22.04.1 LTS)
Download dynalist.tar.gz
Extract dynalist.tar.gz
cd dynalist-1.0.6
./dynalist

Logging to  /home/$USER/.config/Dynalist/dynalist/dynalist-2022-11-27-17-42-10.log
Platform: linux
App path is: /home/$USER/Downloads/Tools/dynalist-1.0.6/resources/
Data path is: /home/$USER/.config/Dynalist/dynalist
[App] /home/$USER/Downloads/Tools/dynalist-1.0.6/dynalist
[App] App running, version 1.0.6
[Updater] Checking for updates...
[Updater] https://dynalist.io/standalone/check?platform=linux
[Loader] Trying to load main file from /home/$USER/Downloads/Tools/dynalist-1.0.6/resources/dynalist.asar/main.js
[Loader] Executing main function
Dynalist loading /home/$USER/Downloads/Tools/dynalist-1.0.6/resources/dynalist.asar
/home/$USER/Downloads/Tools/dynalist-1.0.6/resources/dynalist.asar/www/index.html
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[Updater] Downloading package "dynalist" from "https://dynalist.io/standalone/download?file=dynalist-1.5.1.asar.gz"
[39975:1127/174211.187246:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

Expected result

What do you expect to see after carrying out the steps above?

I expect to see the Dynalist application interface start up and remain on the screen for more than 2 seconds.

Actual result

Instead of the expected result, what happened?

I see the stdout output as listed above, and a Dynalist GUI screen flash onto the screen briefly.

Environment

Which operating system are you using?
Kubuntu Linux, Jammy Jellyfish (22.04.1 LTS)
Linux 5.15.0-53-generic #59-Ubuntu SMP x86_64 GNU/Linux

Which browser are you using?
Not applicable, Dynalist works just fine in my browser.

If you’re using a desktop or mobile app, what’s the version number of Dynalist?
1.0.6

Are you using any third-party scripts for Dynalist, e.g. PowerPack?
No.

Additional information

Anything else you think would help our investigation, like a screenshot or a log file? You can drag and drop screenshots to this box. For large amount of text, try putting them into something like Pastebin.

$ nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 2060M   Off  | 00000000:01:00.0  On |                  N/A |
| N/A   45C    P8     8W /  N/A |   4031MiB /  6144MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A     18746      C   python                           4019MiB |
+-----------------------------------------------------------------------------+

Additional comments

BigChungus · December 27, 2022, 2:14am

You could try forcing the discrete GPU vs the integrated GPU and see if that helps https://www.electronjs.org/docs/latest/api/command-line-switches

dynalist --force_high_performance_gpu

dynalist --force_low_power_gpu

Do you get this problem with Chrome or other Electron apps such as https://code.visualstudio.com/?

Greg_Torrance · May 10, 2023, 5:18pm

I was having the exact same problem as the original poster. I’m running a fresh install of Linux Mint 21.1. Though I was able to get Dynalist working initially, it stopped working. I’m fairly sure the issue is related to switching to the “nvidia-driver-530” driver from the default “xserver-xorg-video-neuveau” driver. (I’ve had issues with Nvidea drivers before on Linux.) Though I did not revert the driver change to confirm this theory, I did stumble on the following option which caused the issue to go away:

dynalist --disable-gpu-sandbox

Everything seems to work fine now.

(BTW, I tried the suggestions above, but still encountered the error. Also Visual Studio Code works fine. No issues there.)

D_P · December 22, 2024, 2:49am

I’m experiencing the same issue in December 2024 on Debian 12 (bookworm) with NVIDIA driver 535.183.01 and GTX 1080.

Like Greg_Torrance mentioned, the --disable-gpu-sandbox workaround does resolve the issue. However, I’ve gathered some additional debug logs that might help identify the root cause.

When running with --enable-logging --enable-gpu-service-logging, the logs show:

VAAPI initialization failures
Multiple GPU process crashes (9 attempts)
Failed fallbacks through different rendering modes (native → swiftshader → disabled)

Other Electron apps like VS Code work fine on my system, suggesting this might be specific to how Dynalist handles GPU acceleration and sandboxing.

Full debug logs show a chain of failures:

[43602:1219/100602.316045:INFO:cpu_info.cc(53)] Available number of cores: 12
[1:1219/100602.316181:INFO:cpu_info.cc(53)] Available number of cores: 12
[43602:1219/100602.316138:VERBOSE1:zygote_main_linux.cc(217)] ZygoteMain: initializing 0 fork delegates
[1:1219/100602.316268:VERBOSE1:zygote_main_linux.cc(217)] ZygoteMain: initializing 0 fork delegates
[43599:1219/100602.436935:VERBOSE1:pref_proxy_config_tracker_impl.cc(186)] 0x1b42f85cb840: set chrome proxy config service to 0x1b42f8a9aa80
[43599:1219/100602.462698:VERBOSE1:pref_proxy_config_tracker_impl.cc(186)] 0x1b42f8d398c0: set chrome proxy config service to 0x1b42f8e17e00
[43599:1219/100602.464591:VERBOSE1:device_event_log_impl.cc(216)] [10:06:02.464] Bluetooth: EVENT: bluetooth_api.cc:74 BluetoothAPI: 0x1b42f8726480
[43599:1219/100602.478551:VERBOSE1:bus.cc(703)] Requested to remove an unknown filter function: 1 with associated data: 0x1b42f8df1820
[43599:1219/100602.501343:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.bluez"

[43599:1219/100602.501558:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.bluez"

[43599:1219/100602.502027:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.chromium.Bluetooth"

[43599:1219/100602.502215:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.chromium.Bluetooth"

[43599:1219/100602.509335:VERBOSE1:bus.cc(681)] Filter function already exists: 1 with associated data: 0x1b42f8b10410
[43599:1219/100602.509382:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.bluez"

[43599:1219/100602.509703:VERBOSE1:bus.cc(681)] Filter function already exists: 1 with associated data: 0x1b42f8b10410
[43599:1219/100602.509730:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.bluez"

[43599:1219/100602.509898:VERBOSE1:bus.cc(681)] Filter function already exists: 1 with associated data: 0x1b42f8df1270
[43599:1219/100602.509922:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.chromium.Bluetooth"

[43599:1219/100602.510246:VERBOSE1:bus.cc(681)] Filter function already exists: 1 with associated data: 0x1b42f8df1270
[43599:1219/100602.510272:VERBOSE1:bus.cc(884)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.chromium.Bluetooth"

[43662:1219/100602.522982:INFO:cpu_info.cc(53)] Available number of cores: 12
[43662:1219/100602.539105:VERBOSE1:document.cc(3974)] Document::DispatchUnloadEvents() URL = <null>
[43662:1219/100602.539222:VERBOSE1:document.cc(4054)] Actually dispatching an UnloadEvent: URL = <null>
[43662:1219/100602.541749:VERBOSE1:script_context.cc(273)] Created context:
  extension id:           (none)
  frame:                  0xe1cace22e8
  URL:                    
  context_type:           WEB_PAGE
  effective extension id: (none)
  effective context type: WEB_PAGE
[43662:1219/100602.542301:VERBOSE1:script_context.cc(273)] Created context:
  extension id:           (none)
  frame:                  (nil)
  URL:                    
  context_type:           UNSPECIFIED
  effective extension id: (none)
  effective context type: UNSPECIFIED
[43662:1219/100602.542392:VERBOSE1:dispatcher.cc(385)] Num tracked contexts: 1
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[43632:1219/100602.554531:VERBOSE1:vaapi_wrapper.cc(607)] InitializeVaDriver_Locked(): vaInitialize failed: unknown libva error
[43632:1219/100602.558612:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100602.952424:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100602.952459:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 1 time(s)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[43704:1219/100603.042081:VERBOSE1:vaapi_wrapper.cc(607)] InitializeVaDriver_Locked(): vaInitialize failed: unknown libva error
[43704:1219/100603.046100:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100603.585457:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100603.585833:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 2 time(s)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[43718:1219/100603.680820:VERBOSE1:vaapi_wrapper.cc(607)] InitializeVaDriver_Locked(): vaInitialize failed: unknown libva error
[43718:1219/100603.684821:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100604.283255:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100604.283303:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 3 time(s)
[43732:1219/100604.296710:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for swiftshader
[43732:1219/100604.296897:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[43732:1219/100604.303363:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100604.873630:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100604.873686:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 4 time(s)
[43755:1219/100604.882708:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for swiftshader
[43755:1219/100604.882853:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[43755:1219/100604.889084:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100605.426175:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100605.426204:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 5 time(s)
[43768:1219/100605.435701:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for swiftshader
[43768:1219/100605.436152:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[43768:1219/100605.442384:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100606.022887:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100606.022909:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 6 time(s)
[43787:1219/100606.027170:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for disabled
[43787:1219/100606.027248:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[43787:1219/100606.028995:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100606.494212:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100606.494264:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 7 time(s)
[43807:1219/100606.498534:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for disabled
[43807:1219/100606.498621:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[43807:1219/100606.500567:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100607.212326:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100607.212350:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 8 time(s)
[43821:1219/100607.216456:WARNING:vaapi_wrapper.cc(588)] VAAPI video acceleration not available for disabled
[43821:1219/100607.216550:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[43821:1219/100607.218154:VERBOSE1:sandbox_linux.cc(69)] Activated seccomp-bpf sandbox for process type: gpu-process.
[43599:1219/100607.876084:ERROR:gpu_process_host.cc(1003)] GPU process exited unexpectedly: exit_code=159
[43599:1219/100607.876109:WARNING:gpu_process_host.cc(1317)] The GPU process has crashed 9 time(s)
[43599:1219/100607.876123:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.

Would it be possible to update Dynalist’s Electron version to match what newer apps like VS Code are using? This might resolve the issue since VS Code handles GPU acceleration without problems on the same system.