nvtop icon indicating copy to clipboard operation
nvtop copied to clipboard

nvtop crashes immediately on startup in the presence of an intel iGPU

Open owlshrimp opened this issue 7 months ago • 3 comments

I have an 11th gen intel processor with an iGPU. previously, with that iGPU disabled and libraries/drivers not installed, nvtop worked perfectly with my nvidia GPU. Following the installation of the relevant drivers and toolkits for openCL and SYCL on that integrated iGPU, nvtop has started crashing immediately on startup with the following message:

nvtop: ./src/extract_gpuinfo_intel.c:230: parse_drm_fdinfo_intel: Assertion `!cache_entry_check && "We should not be processing a client id twice per update"' failed.
Aborted (core dumped)

Previously it used to send a message about not supporting intel GPUs or something, with the options "ok" and "don't show again" where it would immediately crash after selecting ok. After selecting "don't show again" it just immediately crashes on startup.

Related to #271 (but more specific about the problem).

owlshrimp avatar Jun 07 '25 20:06 owlshrimp

Have you tried using the latest version or the appimage? Like you noticed it was an issue of older versions of nvtop that was fixed a while ago. Unfortunately I cannot do much for the nvtop packaged by distributions that are not up-to-date.

Syllo avatar Jun 28 '25 13:06 Syllo

This seems to be fixed in the latest released appimage. Guessing that the version shipped by ubuntu is too old.

owlshrimp avatar Jun 30 '25 03:06 owlshrimp

Ubuntu 24.04 distributes v3.0.2-1. There is a launchpad package bug for the issue, if ppl want to chime in or mark that they're affected, maybe we can push the maintainer to bump the version.

https://bugs.launchpad.net/ubuntu/+source/nvtop/+bug/2110352

On a side note, the Intel Readme item about enabling the SET_CAP privilege on the nvtop binary seems to fix this (at least until the next version of the package is installed?). My system was working, then it wasn't, I didn't pay close attention to the nvtop package versions in-between working and not-working I hypothesize it was a kernel update or package update that broke things.

salderma avatar Jul 10 '25 17:07 salderma