NVIDIA / NVIDIA/nvImageCodec

Invalid encode_status error codes

Open
#43 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Jupyter Notebook
Stars
159
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Version

0.6.0

Describe the bug.

I have some code that works fine in the Jetson Orin Nano devkit using version 0.6.0. Haven't figured out how to adapt to 0.7.0 yet.

When I try to run the code in the production board I find different issues. First time I got an encode_status value of 65535.

I went through different combinations of ways to install the library, and how to build the C++ project. Right now I finally built it on the production board itself, using the 0.6.0 tarball distribution. Again, it works fine in the devkit. In the production board I now get an encode_status of 33, another invalid error code.

I am not sure how to proceed finding any clues. There should be little to no difference in the prod and dev systems. I was trying to use the debug message callback code from the codebase, but I got nothing yet. How exactly do I set that up? And what else can I try?

By the way, sometimes I also get this weird memory errors, I won't be able to allocate memory and I get the message

NvMapMemAllocInternalTagged: 1075072515 error 12
NvMapMemHandleAlloc: error 0

This goes away if I reboot. I wonder if it's related. But I get the invalid error code even with no sign of that other memory issue.

I also posted about this issue in https://forums.developer.nvidia.com/t/nvimgcodec-produces-status-code-65535

Minimum reproducible example

Environment details

Relevant log output
production board AVerMedia D131L (Jetson Orin Nano 8GB)
Other/Misc.

No response

Check for duplicates
  • I have searched the open bugs/issues and have found no duplicates for this bug report

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 with the debug message callback code referenced in the issue and reproduce the encode_status values on the Jetson Orin Nano production board using the 0.6.0 tarball. Compare the production and devkit environments, including the reported NvMapMem allocation errors and the NVIDIA forum thread. Done means identifying a reproducible cause or narrowing the status-code and memory behavior to a documented environment difference.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
24/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.