multiple threads create their own instance calls nvjpegEncodeYUV() return NVJPEG_STATUS_EXECUTION_FAILED
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.6k
- Forks
- 2.4k
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
hi!
I create separate instances in multiple threads and call nvjpegEncodeYUV(Handle, EncoderState, EncoderParams, &DBuffer, NVJPEG_CSS_GRAY, Width, Height, Stream); return NVJPEG_STATUS_EXECUTION_FAILED. And it is OK when the last parameter is NULL or cudaStreamPerThread.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the multithreaded call to nvjpegEncodeYUV() with separate instances and an explicit CUDA stream, comparing it with NULL and cudaStreamPerThread. Investigate why the explicit-stream case returns NVJPEG_STATUS_EXECUTION_FAILED, and consider the issue resolved when independent threads succeed with the intended stream argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100