We're trying to start a GStreamer pipeline using C++ libraries, in which we start it through a JNI interface from a Scala application. The initiated pipeline sometimes causes a segfault which as a result crashes the JVM entirely and makes the entire application unavailable for other pipelines to run or even allows existing ones to continue running.
The strive is not having the behavior of segfault. Of course, as might already be known, a segfault can be prevented only when finding the memory leak issue core origin problem which can be wrong applicative use or implementation, but in general, the expected behavior is basically not experiencing segfault from the first place.
The use of the rtspclientsink element, in some cases, causes a segfault for the library "libgstrtsp.so" in the function call write_bytes().
The bug doesn't occur in high frequency, and does not necessarily have a strict pattern to allow indicating the source of the issue, unfortunately.
Don't have any.
Can't do any solution due to being an internal issue of GStreamer as it seems.
Didn't find any.
I have the crash report, but don't wish for the code signature or anything be visible to anyone who sees this ticket, so either we make it confidential or please tell which parts of the JVM crash reports are needed to further investigate the problem.
Of course, tell me what is easier and I'll provide as asked
Hello,
We're developing a C++ application that uses GStreamer headers. The solution we have is making an RTSP connection using the rtspclientsink element, which mainly reads UDP ports, encapsulates the data with AAC encoding, and then sends that data via RTSP to an RTSP server.
We've recently experienced an issue that we're starting a GStreamer pipeline that at the moment we start it, we receive the following exception:
ERROR: Caught a segmentation fault while loading plugin file:
/usr/local/lib/x86_64-linux-gnu/gstreamer-1.0/libgstrtpmanager.so
Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.
It seems that it doesn't happen all the time, and actually changes the behavior when the application restarts, while having the same GStreamer installing/configured dependencies.
We're using GStreamer from the gst-build, which uses version 1.18.4 if that helps.
By any chance, can you tell why the error is happening and maybe a way to solve it?
Thanks! :)
Hello,
We've recently moved to using gst-build project for compiling our GStreamer dependencies for our GStreamer based application.
We're currently using GStreamer v.1.18.4.
For some reason, we've started to experience a case of failing to initialize plugins, and specifically libgstvalidatessim.so.
These are the logs we've received from GST_DEBUG logs:
GST_PLUGIN_LOADING gstplugin.c:535:gst_plugin_register_func:[00m plugin "/usr/local/lib/x86_64-linux-gnu/gstreamer-1.0/validate/libgstvalidatessim.so" failed to initialise
I've saw there are many cases of some sort but for other plugins regarding the meson build system. Is there a chance it has any relations to those issues or it's maybe a new use case?
Thanks :)