How to handle the warning.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant

The pipeline will get the warning on TX2

nvidia@tegra-tx2:~$ gst-launch-1.0 filesrc location=1.h264 ! h264parse ! nvv4l2decoder bufapi-version=true ! nvvideoconvert  name=vidconv ! 'video/x-raw(memory:NVMM),format=(string)RGBA,width=1024,height=540' ! fakesink
Setting pipeline to PAUSED ...
Opening in BLOCKING MODE
Pipeline is PREROLLING ...
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:01.041156480
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

And the dmesg output:

nvidia@tegra-tx2:~$ dmesg -w
[ 3577.616836] nvmap_alloc_handle: PID 13880: gst-launch-1.0: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.

TX2 jetson version

nvidia@tegra-tx2:~$ head -n 1 /etc/nv_tegra_release
# R32 (release), REVISION: 2.1, GCID: 16294929, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 13 04:45:36 UTC 2019

1.h264
extract code : 0zCUhDep

How to handle the warning?
Thanks

Hi,
The print is harmless, you can ignore it.

2 Likes