[GSD-13675] Lunar Lake: large Level Zero allocation leaks system memory after process exit
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- cpp, linux, ubuntu
- Ambito
- backend, computer-graphics, operating-systems
Direzione di ricerca
Start by compiling and running the attached ze-memory-lifetime-repro.c with the 21,022 MiB allocation, then compare it with the 256 MiB case using free -h before and after cleanup. Trace the Level Zero allocation, zeMemFree(), context destruction, and process-exit paths; the issue is done when the large allocation no longer leaves system memory unavailable after exit.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Pre-submission Checklist
- I am using the latest GPU driver version published by
ppa:kobuk-team/intel-graphicsfor Ubuntu 26.04 - I searched for similar issues and found none
System Information
GPU Hardware
Intel Core Ultra 7 258V / Lunar Lake Arc 140V (8086:64a0, rev 04)
DRI Devices Information
0 crw-rw----+ 1 root video 226, 1 /dev/dri/card1
0 crw-rw----+ 1 root render 226, 128 /dev/dri/renderD128
pci-0000:00:02.0-card -> ../card1
pci-0000:00:02.0-render -> ../renderD128
GPU Detailed Information (lspci output)
00:02.0 VGA compatible controller: Intel Corporation Lunar Lake [Intel Arc Graphics 130V / 140V] (rev 04)
Subsystem: Lenovo Device 233d
Region 0: Memory at 204e000000 (64-bit, prefetchable) [size=16M]
Region 2: Memory at 2000000000 (64-bit, prefetchable) [size=256M]
Kernel driver in use: xe
Kernel modules: xe
Driver Version
libze-intel-gpu1 26.31.39395.14-1~26.04~ppa1
Installed GPU Driver Packages
intel-ocloc 26.31.39395.14-1~26.04~ppa1
intel-opencl-icd 26.31.39395.14-1~26.04~ppa1
libigc2 2.40.13+ds1-1~26.04
libigdfcl2 2.40.13+ds1-1~26.04
libigdgmm12 22.10.1-1~26.04~ppa1
libze-dev 1.32.0-1~26.04~ppa1
libze-intel-gpu1 26.31.39395.14-1~26.04~ppa1
libze1 1.32.0-1~26.04~ppa1
Driver Installation Details
Installed from ppa:kobuk-team/intel-graphics.
Linux Distribution
Other: Ubuntu 26.04.1 LTS
Kernel Version & Boot Parameters
Kernel: 7.0.0-34-generic
BOOT_IMAGE=/vmlinuz-7.0.0-34-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash mitigations=off isolcpus=managed_irq,0-3
xe 4415488 26
gpu_sched 69632 1 xe
drm_gpuvm 57344 1 xe
drm_buddy 28672 1 xe
drm_ttm_helper 20480 1 xe
ttm 135168 2 drm_ttm_helper,xe
drm_exec 12288 2 drm_gpuvm,xe
drm_suballoc_helper 24576 1 xe
Issue Description
Actual Behavior
A large Level Zero device allocation leaves approximately 13.6 GiB of system memory unavailable after zeMemFree() returns success, the Level Zero context is destroyed, and the process exits. The memory is recovered only by rebooting.
With libze-intel-gpu1 26.31.39395.14, MemAvailable fell from 26,066,300 kB to 11,836,096 kB and remained there after approximately 50 seconds. The reproducer had exited and no xe fault or reset was logged.
A 256 MiB allocation using the same reproducer frees normally.
Expected Behavior
The backing system memory should become reclaimable after zeMemFree(), context destruction, and process exit.
Reproduction Rate
Always reproduces — 100%
Steps to Reproduce
Using the attached reproducer:
free -h
./ze-memory-lifetime-repro 21022
sleep 20
free -h
The program allocates 21,022 MiB with ZE_RELAXED_ALLOCATION_LIMITS_EXP_FLAG_MAX_SIZE, touches the allocation from the GPU, synchronizes, frees it, destroys the context, and exits normally.
Diagnostics & Logs
System Logs / dmesg Output
No GPU fault or reset was logged during reproduction.
Reproducer Information
Source Code / Reproducer
While this issue was originally encountered using a SYCL build of llama.cpp, the reproducer above relies only on raw Level Zero.
Command Line / Application Details
./ze-memory-lifetime-repro 21022
A 256 MiB control run does not leak:
./ze-memory-lifetime-repro 256
- Lingua principale
- C++
- Stelle
- 1.5k
- Fork
- 303
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di intel/compute-runtime
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
intel/compute-runtime#943 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
intel/compute-runtime#1031 ·
-
Difficoltà 4/5 1-2 giorni Idoneità per principianti 54/100
intel/compute-runtime#1030 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
intel/compute-runtime#1029 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
intel/compute-runtime#1026 ·
Tutte le issue di intel/compute-runtime
Issue simili
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
metasequoiaime/msime#9113 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
tone-3000/tone3000-plugin#257 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Locked plugin flip-flops position on every refresh after being disabledForse già presa @Illustar0 l’ha presa oggi. Apertaissue report
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
ModOrganizer2/modorganizer#2449 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement P5
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
open-astro/AlpacaBridge#1468 ·
I maintainer di solito rispondono entro 1 giorno