NVIDIA / NVIDIA/TensorRT

OOM error of TensorRT 10.12 when running engine build on GPU NVIDIA T4

Open
#4,582 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Module:Engine Build
Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

Description

Hi,

My application build multiple TensorRT engines from ONNX models and they are run in a pipeline.
The problem I have is that I'm getting random OOM errors when building the first engine. I always build these engines sequentially. I deploy my application in a AWS cluster with g4dn.xlarge EC2 instance so I run this in NVIDIA T4 with 15gb which it is more than enough. My pipeline of models has a GPU memory peak of roughly 7GB during the engine build so there is enough memory.

This error happens randomly, maybe 1 out of 30 jobs fail with this error.

I run my application using docker with argument "--gpus all" and using base image nvidia/cuda:12.8.1-runtime-ubuntu22.04

Environment

TensorRT Version: 10.12

NVIDIA GPU: T4

NVIDIA Driver Version: 570.172.08

CUDA Version: 12.8.1

CUDNN Version: not used

Operating System: ubuntu 22

Relevant Files

Please find attached logs of the error:

trt_logs_jenkins.txt

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached trt_logs_jenkins.txt log and the reported environment: TensorRT 10.12, CUDA 12.8.1, Ubuntu 22.04, and an NVIDIA T4 in an AWS g4dn.xlarge instance. Reproduce the sequential engine builds in the Docker setup and determine why intermittent GPU out-of-memory errors occur; done means the cause is identified and a reliable correction or reproduction is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
machine-learning, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.