IJPE sample prints unconditional debug lines ("TEST: Append a pushbuffer...", "GOT VALID FENCES") via `libnvvideo.so`

Autonomous Vehicles DRIVE AGX Thor DRIVE AGX Thor General
1

Software Version
DRIVE OS 7.0.3
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Thor Developer Kit (940-63960-0010-000)
DRIVE AGX Thor Developer Kit (940-63960-0012-000)
other

Host Machine Version
native Ubuntu Linux 24.04 Host installed with DRIVE OS Docker Containers
other

Issue Description:

Running the stock `nvm_ijpe_sci` sample (`/drive/drive-linux/samples/nvmedia_6x/ijpe/`) prints these two lines per encode submission, regardless of the sample’s own `-v` log level:

TEST: Append a pushbuffer with channel's syncpoint increment ********

GOT VALID FENCES

Repro:

./nvm_ijpe_sci -f fisheye_1280_1080_yuv420.yuv -pf 1 -fr 1280x1080 -q 50 -of /tmp/out.jpg

We found that NvMediaIJPEFeedFrame(), NvMediaIJPEFeedFrameQuant(), and NvMediaIJPEFeedFrameRateControl() all print this, regardless of which one is used.

Questions:

1. Is this expected/intentional debug output in `libnvvideo.so`, or a bug (looks like leftover test/debug logging, given the string literally says “TEST:”)?

2. If it’s a known issue, which DRIVE OS version has it fixed/removed?

3. Is there any supported way to disable it (env var, log-level API, config)?

4

Dear @yungchen.sun.802 ,
Let me verify this on recent release(DOS 7.2.5) . Also, just want to check if it causing any issue in your application?

6

Thanks for checking! These debug messages keep flooding stdout, making it harder for us to identify our own logs.