Skip to content

bug: tauri-plugin-hardware reporting incorrect VRAM size of Vulkan enabled GPU on Linux #6591

@qnixsynapse

Description

@qnixsynapse

Version: 0.7.0 nightly with PR #6584

Describe the Bug

The tauri-plugin-hardware API is reporting an incorrect value for total_memory (VRAM) for Vulkan supported GPUs when the application is built in a GitHub Actions CI runner and then run on a local machine running Arch Linux. The reported value is usually significantly higher than the actual GPU memory. This issue does not seem to occur in local builds.

Steps to Reproduce

  1. Download prebuilt Jan app from Actions
  2. Run it in modern distros such as Arch Linux
  3. check model support indicator of an unsupported model or click on optimise settings button and check logs

Screenshots / Logs

For Intel Arc A750 LE which has 8GB of VRAM, the reported struct from tauri-plugin-hardware is as follows:
[GpuInfo { name: "Intel(R) Arc(tm) A750 Graphics (DG2)", total_memory: 180961176, vendor: Intel, uuid: "8680a156-0800-0000-0300-000000000000", driver_version: "Mesa 25.2.3-arch1.2", nvidia_info: None, vulkan_info: Some(VulkanInfo { index: 0, device_type: "DISCRETE_GPU", api_version: "1.4.318", device_id: 22177 }) }]

Here VRAM reported by the hardware-plugin is 180961176 MB which is 180 TB which is surely garbled!

Operating System

  • MacOS
  • Windows
  • Linux (currently reproducible on Linux on discrete Intel GPU)

Metadata

Metadata

Assignees

No one assigned

    Labels

    os: linuxLinux issuesplatform: desktopDekstop related issuerustPull requests that update rust code

    Type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions