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

H264EncoderNvCodec uses hard-coded number of Encoder Buffers, which causes problems if there is a delay associated with other modules #358

Closed
kushaljain-apra opened this issue Jun 3, 2024 · 0 comments · Fixed by #360
Assignees

Comments

@kushaljain-apra
Copy link
Collaborator

Describe the bug
Currently, H264EncoderNvCodec Module uses a hard-coded number of Encoder Buffers, which can cause an issue if there is a delay associated with other modules. For example, H264Decoder Module

To Reproduce
Steps to reproduce the behavior:

  1. Run the H264Decoder_tests in which one of the tests uses both H264EncoderNvCodec and H264Decoder
  2. Test execution stops in the middle if the number of free encoder buffers reaches zero before they are released by the H264 Decoder because it uses H264EncoderNvCodec memory pool to allocate the frame which will be released only when its process get completed by H264 Decoder.

Expected behavior
Tests should pass without any interruption.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. chrome, safari]
  • Cuda Version [e.g. 22]
  • Architecture [e.g. x86_64, arm64]

Additional context
Add any other context about the problem here.

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant