Vasily Galkin

I looked into the great open databse for this GPU - https://www.vulkan.gpuinfo.org/listreports.php?devicename=Radeon+Vega+Frontier+Edition It seems that [report with older windows driver version ](https://www.vulkan.gpuinfo.org/displayreport.php?id=2843#memory) actually reports 24GB heap of internal memory. This...

Thanks for reply (I redacted your message to hide huge log in spoiler). So, it seems to be not specific for memtest_vulkan. From the memtest_vulkan side - I can't see...

What is your system RAM size? Maybe PRO driver model somehow tries to extend the address space accessible to GPU via shared system memory, but that mechanism cant be used...

Interesting. Can you post vulkan-info reporting into databse one more time, now with this option disabled? I'll compare the reports to see if this option state can be somehow determined...

Af far as I understand - nixpkgs concept assumes that all paths to the dependecnies are somehow embedded in the binary itself and there is no some per-application `ld.so.conf` file...

Hi. Unfortunately `memtest_vulkan` does not support Kepler-base nvidia GPUs (due to their memory organization). Typically they error-out with `This device lacks support for DEVICE_LOCAL+HOST_COHERENT memory type`, but for your case...

The "8GB llvmpipe" is a software-based vulkan implementation/emulation executed on the main CPU. It is a some (not effective I suppose) CPU+main memory test, but it does not touch GPU...

In short: please enable verbose mode by renaming the executable to memtest_vulkan_verbose, run again and attach here its output. Thanks for reporting. The issue looks very strange, however given that...

@bagusnl I collapsed he long log and created a separate issue for your case. It seems to be unrelated - caused by **total** GPU memory size printed as "1GB" in...

`heap size 7.8GB budget 0.4GB usage 0.0GB flags=DEVICE_LOCAL` from your log - the driver reports that only 0.4GB out of 7.8GB is the allowed memory budget for application This is...