Segmentation fault using nv_obj_enc + nvmultiurisrcbin + glog

[maksym.shtembuliak]

• Hardware Platform (Jetson / GPU) Laptop with NVIDIA GPU RTX 4060
• DeepStream Version 7.0
• TensorRT Version 8.6.1.6-1+cuda12.0
• NVIDIA GPU Driver Version Driver Version: 550.107.02 CUDA Version: 12.4
• Issue Type Questions

Greetings.
Faced an interesting behavior of rest server (nvds_rest_server) used inside nvmultiurisrcbin, in conjunction with nvds_obj_enc and glog.
Here is some sample code that reproduces the problem:

#include "gstnvdsmeta.h"
#include <nvbufsurface.h>
#include <nvds_obj_encode.h>
#include <nvds_rest_server.h>
#include <glog/logging.h>

int main(int argc, char *argv[]) {
    google::InitGoogleLogging(argv[0]);

    nvds_obj_enc_create_context(0);

    NvDsServerConfig server_conf = {};
    server_conf.ip = "localhost";
    server_conf.port = "9000";

    NvDsServerCallbacks server_cb = {};

    (void*)nvds_rest_server_start(&server_conf, &server_cb);

    while (true) {};
}

If we run the code as is, it causes a segmentation fault inside libcivetweb.so when receiving/parsing a rest request.
The version of the glog library I’m using is 0.29.2, installed via apt install in ubuntu 22.04.
If I comment out the glog or nvds_obj_encode API calls, rest server starts processing requests correctly and the error does not occur.

What is the cause of this behavior and how to resolve the conflict?

[yuweiw]

Since it’s a problem of using nvds_obj_enc and glog together, could you try to reproduce that with our sources\apps\sample_apps\deepstream-image-meta-test?
If it can be reproduced in our demo, we can analyze the problem much faster.

[maksym.shtembuliak]

It looks like you are right about a problem of using nvds_obj_enc and glog together.
Interestingly, the problem did not manifest itself until some time later when we decided to add nvmultiurisrcbin to our pipeline.
The problem is very easy to reproduce in any code.
Here is an example of a patch that reproduces the problem in deepstream-image-meta-test.
Also, don’t forget to install glog via apt install libgoogle-glog-dev and add it to your Makefile. You should also add -lnvds_rest_server to the Makefile.

--- a.c	2024-04-29 02:27:33.000000000 +0300
+++ b.c	2024-10-16 13:22:06.657971283 +0300
@@ -26,6 +26,9 @@
 #include "nvds_obj_encode.h"
 #include "gst-nvmessage.h"
 
+#include <nvds_rest_server.h>
+#include <glog/logging.h>
+
 #define MAX_DISPLAY_LEN 64
 
 #define PGIE_CLASS_ID_VEHICLE 0
@@ -447,6 +450,16 @@
 int
 main (int argc, char *argv[])
 {
+  google::InitGoogleLogging(argv[0]);
+
+  NvDsServerConfig server_conf = {};
+  server_conf.ip = "localhost";
+  server_conf.port = "9000";
+
+  NvDsServerCallbacks server_cb = {};
+
+  (void*)nvds_rest_server_start(&server_conf, &server_cb);
+
   GMainLoop *loop = NULL;
   GstElement *pipeline = NULL, *streammux = NULL, *sink = NULL, *pgie = NULL,
       *nvvidconv = NULL, *nvosd = NULL, *tiler = NULL;

Well, and accordingly, you need to send a POST request in order to get a segmentation fault.

  curl -XPOST 'http://localhost:9000/api/v1/stream/add' -d '{
    "key": "sensor",
    "value": {
        "camera_id": "uniqueSensorID1",
        "camera_name": "front_door",
        "camera_url": "file:///opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h264.mp4",
        "change": "camera_add",
        "metadata": {
            "resolution": "1920 x1080",
            "codec": "h264",
            "framerate": 30
        }
    },
    "headers": {
        "source": "vst",
        "created_at": "2021-06-01T14:34:13.417Z"
    }
  }'

Thanks!

[yuweiw]

I have tried that with our deepstream-server demo. The code does not compile properly.
Could you provide us the Makefile and diffs of our code based on deepstream-server?
Since Gstreamer has a perfect log mechanism, why would you want to use the GoogleLog?

[maksym.shtembuliak]

Sure. Below is the patch for the deepstream-server application.
Using glog in the project is the customer’s wish.
patch.txt (1.5 KB)

[yuweiw]

I have tried that with our latest version DS7.1. It worked normally with your patch. Could you try that on DS7.1?

[yingliu]

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