Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[calibrator.cu::cuCalibrator::absTensorMax::146] #3830

Open
xiao-lin-hub opened this issue Apr 27, 2024 · 1 comment
Open

[calibrator.cu::cuCalibrator::absTensorMax::146] #3830

xiao-lin-hub opened this issue Apr 27, 2024 · 1 comment
Assignees
Labels
triaged Issue has been triaged by maintainers

Comments

@xiao-lin-hub
Copy link

[04/27/2024-11:58:49] [TRT] [E] 1: [calibrator.cu::cuCalibrator::absTensorMax::146] Error Code 1: Cuda Runtime (invalid resource handle)
[04/27/2024-11:58:49] [TRT] [E] 1: [calibrator.cu::cuCalibrator::absTensorMax::146] Error Code 1: Cuda Runtime (invalid resource handle)
[04/27/2024-11:58:49] [TRT] [E] 1: [calibrator.cu::cuCalibrator::absTensorMax::146] Error Code 1: Cuda Runtime (invalid resource handle)
[04/27/2024-11:58:49] [TRT] [E] 1: [reformatRunner.cpp::nvinfer1::rt::cuda::ReformatRunner::execute::613] Error Code 1: Cuda Runtime (invalid resource handle)
[04/27/2024-11:58:49] [TRT] [E] 3: [engine.cpp::nvinfer1::rt::Engine::~Engine::307] Error Code 3: API Usage Error (Parameter check failed at: engine.cpp::nvinfer1::rt::Engine::~Engine::307, condition: mObjectCounter.use_count() == 1. Destroying an engine object before destroying objects it created leads to undefined behavior.
)
[04/27/2024-11:58:49] [TRT] [E] 2: [calibrator.cpp::nvinfer1::builder::calibrateEngine::1181] Error Code 2: Internal Error (Assertion context->executeV2(&bindings[0]) failed. )

@zerollzeng
Copy link
Collaborator

[04/27/2024-11:58:49] [TRT] [E] 1: [calibrator.cu::cuCalibrator::absTensorMax::146] Error Code 1: Cuda Runtime (invalid resource handle)

Looks like cuda issue, does it reproduce in the TensorRT docker container?

@zerollzeng zerollzeng self-assigned this May 3, 2024
@zerollzeng zerollzeng added the triaged Issue has been triaged by maintainers label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged Issue has been triaged by maintainers
Projects
None yet
Development

No branches or pull requests

2 participants