`nvds_get_user_meta_type` sometimes returns different values for same input at different

  • Hardware Platform: Jetson AGX Orin
  • DeepStream version 6.2
  • Issue Type: bug


I have noticed some confusing behavior from nvds_get_user_meta_type in DeepStream 6.2. It appears that given the same input, two different calls to nvds_get_user_meta_type will sometimes give different outputs. Is this nondeterminism expected? The documentation doesn’t explicitly state that two calls with the same input are guaranteed to have the same output, but this seems like a reasonable thing to expect.

To reproduce:

  • initialize some user meta and set its type with nvds_get_user_meta_type(NAME)
  • later, call nvds_get_user_meta_type with same NAME

I encounter this flaky behavior ~0.1% of the time.

Could you provide us with a specific demo you are using to reproduce this issue?

Let me produce a minimum working example

@yuweiw do you know if this function is thread-safe?

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks

Yes. You can also refer to our demo code about it: opt\nvidia\deepstream\deepstream\sources\apps\sample_apps\deepstream-user-metadata-test.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.