You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Atom 1.69.1 AppImage works in Debian 12 with default video card drivers, but after installing Nvidia drivers I get this error that prevents me from launching Atom: [6712:1126/031759.008365:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye
I tried running Atom with this --disable-gpu: ./atom-v1.63.1-x86_64.AppImage --disable-gpu
The --in-process-gpu argument got Atom launching again: ./atom-v1.63.1-x86_64.AppImage --in-process-gpu
However, running the GPU process within the same process as the application, as enabled by the --in-process-gpu flag, is considered less secure due to the increased risk of security vulnerabilities. In a typical setup, the GPU process is isolated in a separate process, which helps contain any potential security breaches within that process. If a vulnerability is exploited in the GPU process, the impact is limited to that process. However, when the GPU process runs within the main application process, any exploited vulnerability could have direct access to everything the main application can access, potentially leading to more severe security implications.
So, ideally, the source code should be modified to run GPU related tasks in a separate process.
The text was updated successfully, but these errors were encountered:
The Atom 1.69.1 AppImage works in Debian 12 with default video card drivers, but after installing Nvidia drivers I get this error that prevents me from launching Atom:
[6712:1126/031759.008365:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye
I tried running Atom with this
--disable-gpu
:./atom-v1.63.1-x86_64.AppImage --disable-gpu
But it produced the same error.
Finally, I found this:
atom/atom#23608
The
--in-process-gpu
argument got Atom launching again:./atom-v1.63.1-x86_64.AppImage --in-process-gpu
However, running the GPU process within the same process as the application, as enabled by the
--in-process-gpu
flag, is considered less secure due to the increased risk of security vulnerabilities. In a typical setup, the GPU process is isolated in a separate process, which helps contain any potential security breaches within that process. If a vulnerability is exploited in the GPU process, the impact is limited to that process. However, when the GPU process runs within the main application process, any exploited vulnerability could have direct access to everything the main application can access, potentially leading to more severe security implications.So, ideally, the source code should be modified to run GPU related tasks in a separate process.
The text was updated successfully, but these errors were encountered: