AOT plugins leak CUDA modules on dynamic-shape changes in TensorRT 11.1/11.2.1
Les mainteneurs répondent en général sous 6 jours
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Clairement spécifiée
- Activité
- Active
- Domaine
- ai-infra-agents, performance
Piste de recherche
Commencez par extraire le reproducer joint et lire run.sh ainsi que replay.cc, puis exécutez les contrôles documentés pour les shapes fixes et les shapes changeantes. Utilisez le comportement signalé lors du chargement des modules et du teardown pour suivre le cycle de vie du plugin AOT ; la tâche est terminée lorsque des changements de shape légaux répétés ont une consommation mémoire bornée et que le teardown de TensorRT libère les modules chargés sans affecter les vérifications de sortie réussies.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Description
GPU memory accumulates when an engine containing an AOT plugin is executed repeatedly with different input shapes in the same execution context. The extra memory remains after destroying the execution context, engine, and TensorRT runtime. Returning to previously used shapes continues the growth.
The attached minimal reproducer uses one hand-written PTX kernel implementing output[i] = 2 * input[i] + 1, registered through tensorrt.plugin.aot_impl. Inference runs in a standalone C++ TensorRT/CUDA process.
The same kernel and one tactic are used for all shapes. The plugin has no allocation or caching code. All outputs match an independent CPU reference exactly. The standard TensorRT affine and convolution controls do not show the retained memory observed with the AOT plugin.
Observed behavior
The clean-environment TensorRT 11.2.1.2 run produces the following results. Each row runs 30,000 requests in a separate process. Memory differences are measured by cudaMemGetInfo between a fresh CUDA context and destruction of all TensorRT objects, without a profiler:
| Engine | Input H/W | Shape changes | Extra memory after TensorRT teardown |
|---|---|---|---|
Standard Scale (2*x + 1) |
Fixed 128x128 | 0 | 0 bytes |
Standard Scale (2*x + 1) |
W alternates 128/192 | 19,999 | 0 bytes |
| Standard 3x3 convolution | Fixed 128x128 | 0 | 0 bytes |
| Standard 3x3 convolution | W alternates 128/192 | 19,999 | 0 bytes |
| One AOT affine plugin | Fixed 128x128 | 0 | 0 bytes |
| One AOT affine plugin | W alternates 128/192 | 19,999 | 50,331,648 bytes (48 MiB) |
The AOT fixed/width pair and standard Scale width control produce the same memory differences on TensorRT 11.1.0.106. These byte counts describe this particular kernel and environment; the issue is continued accumulation, not a particular allocation size or threshold.
A separate TensorRT 11.2.1.2 CUPTI trace records 20,000 successful cuModuleLoadData calls: the first inference plus 19,999 shape changes. Every loaded module's requested kernel is affine. Teardown issues one successful cuModuleUnload, for the last loaded module. The earlier 19,999 modules remain loaded. Module-load caller stacks enter libnvinfer.so.11.
Additional controls reproduce retention when only H changes, or when H/W are transposed between 128x192 and 192x128 with unchanged element count. Three chained AOT plugins retain three modules per shape change. Skipping redundant setInputShape calls does not eliminate retention.
The CUDA context stays alive during the TensorRT-teardown measurements. Separately destroying it with cudaDeviceReset removes the extra memory: both fixed-shape and changing-shape controls reach the same 4 MiB device reading while their processes remain alive, then the 1 MiB idle reading on process exit. Destroying TensorRT execution contexts alone does not have this effect.
Expected behavior
Repeatedly revisiting the same legal input shapes should have bounded resource usage. CUDA modules loaded for AOT execution should be released when they are no longer needed, including when their owning TensorRT objects are destroyed. A long-running process should not accumulate GPU memory with each shape change.
Environment
TensorRT Version: 11.2.1.2; also reproduced on 11.1.0.106. Each engine was built with the same TensorRT version used to execute it. Official, unmodified tensorrt-cu13 Python bindings/libraries.
NVIDIA GPU: RTX 3080 Ti, 12 GiB, compute capability 8.6. One otherwise idle GPU was selected for every experiment.
NVIDIA Driver Version: 580.173.02.
CUDA Version: CUDA toolkit 13.0; nvcc 13.0.88.
CUDNN Version: Not installed in the clean reproducer environment and not required by its source or link command.
Operating System: Ubuntu 24.04.5 LTS, Linux x86_64.
Python Version: 3.13.15, used for engine construction only. NumPy 2.5.1.
C++ compiler: GCC/G++ 13.3.0, C++17. Consumer headers are TensorRT 11.2.1.2; the 11.1 controls use the same shared API subset with their matching 11.1 engine/runtime. The clean 11.2.1 reproduction uses matching headers throughout.
Relevant Files
Attached tensorrt_shape_memory.tar.gz for reproducer.
Steps To Reproduce
Commands or scripts:
Extract tensorrt_shape_memory.tar.gz. Use a CUDA 13 development installation and G++ on Linux. Install NumPy and the matching TensorRT Python packages in an isolated Python 3.13 environment:
python3.13 -m venv .venv
.venv/bin/python -m pip install numpy==2.5.1 tensorrt-cu13==11.2.1.2
Obtain the matching public TensorRT 11.2.1.2 headers:
git clone https://github.com/NVIDIA/TensorRT.git TensorRT-headers
git -C TensorRT-headers checkout c93b7d4893184af4882f9f1862e13a5c64b8677d
Run the attached script on one idle GPU (the reported tests selected GPU 0):
GPU=0 \
PYTHON="$PWD/.venv/bin/python" \
TRT_INCLUDE="$PWD/TensorRT-headers/include" \
TRT_LIB_DIR="$PWD/.venv/lib/python3.13/site-packages/tensorrt_libs" \
CUDA_ROOT=/usr/local/cuda \
REQUESTS=30000 \
bash run.sh
The script compiles the C++ consumer, builds each engine in a separate process, and runs each fixed/width control in another fresh process. Full verbose logs are saved in the output directory it reports.
All engines use input [1,1,H,W], one optimization profile with minimum [1,1,64,64], optimum [1,1,128,128], and maximum [1,1,1152,1152]. The width workload repeats 128x128, 128x128, 128x192. Input/output buffers are allocated once at maximum test size, every request is synchronized, and every output is checked against the CPU reference. The aliased-plugin-I/O preview feature is not enabled.
The affected result reports extra_bytes_after_runtime_destruction: 50331648 with passed: true; all five controls report zero extra bytes. There is no inference exception or numerical failure; GPU memory and module lifetimes are the failing behavior.
Have you tried the latest release?: Tested 11.1.0.106 and 11.2.1.2. TensorRT 11.3.0 has not been tested.
Can this model run on other frameworks?: This is a TensorRT network-API reproducer, not an exported framework model. All outputs match the independent CPU implementations in replay.cc, and the equivalent standard TensorRT Scale control executes without the observed retention.
- Langage dominant
- C++
- Étoiles
- 13.5k
- Forks
- 2.4k
- Merge moyen
- 6 j 21 h
- PR mergées (30 j)
- 3
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de NVIDIA/TensorRT
-
Module:Polygraphy
Difficulté 2/5 1-3 heures Accessibilité débutants 77/100
Les mainteneurs répondent en général sous 6 jours
-
Polygraphy NumPy Top-K sorts unsigned and minimum signed integers incorrectlyPeut-être pris @0z5a l’a pris il y a 16 jours. OuverteModule:Polygraphy
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 6 jours
-
Polygraphy INT32 comparison can overflow and falsely pass at zero tolerancePeut-être pris @0z5a l’a pris il y a 16 jours. OuverteModule:Polygraphy
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 6 jours
-
onnx-graphsurgeon: Graph.toposort() hits RecursionError when a graph has a local function and an If/Loop nodePeut-être pris @gabortar l’a pris il y a 39 jours. OuverteModule:GraphSurgeon
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
Les mainteneurs répondent en général sous 6 jours
-
Polygraphy parse_meta accepts a shape with a missing bracketPeut-être pris @SashaMIT l’a pris il y a 51 jours. OuverteModule:Polygraphy
Difficulté 2/5 1-3 heures Accessibilité débutants 86/100
Les mainteneurs répondent en général sous 6 jours
Toutes les issues de NVIDIA/TensorRT
Issues similaires
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 91/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 69/100
maplibre/maplibre-native#5072 ·
Les mainteneurs répondent en général sous 1 jour
-
[UBSan] spawn_simulator passes null child_options.args to uv_spawn (execvp nonnull violation)Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 79/100
tenstorrent/tt-umd#4017 ·
Les mainteneurs répondent en général sous 3 jours
-
difficulty:easy func:gui prio:low type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
NatronGitHub/Natron#1538 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
hyprwm/hyprsunset#103 · 1 commentaire ·