1000s of dmabuf open file handles reported by lsof

We have a process that does ~6 or so GStreamer encoder/decoder pipelines… Recently I mysteriously busted the system’s max open file limit. When I took a look at the process using lsof I noticed about 6000 (!) lines such as:

myproc 4903 user 2663u  a_inode               0,11         0     10329 dmabuf

I also noted ~250 for /dev/nvhost-vic, ~300 for /dev/nvhost-nvdec and another ~300 for /dev/nvhost-nvdec1

Is this normal/expected?

The process’s current max-open-files limit is at ~8000. Any issue (wrt these dmabuf handles) with increasing this limit?

Please share your L4T release version and steps to reproduce the issue.

We’re on:

R32 (release), REVISION: 2.1, GCID: 16294929, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 13 04:45:36 UTC 2019

We will do the work to come up with a minimal repro. Stay tuned and thank you.

This may not be covered in our SQA tests, so it is probably an issue. We need to reproduce it first so that core teams can evaluate/check if we can include the usecase in future releases.