Alexander Slobodeniuk 7aace62267 aggregator: fix chaining up in GObject "constructed" virtual methods ... This doesn't always bring visible issue, but is formally incorrect: not chaining up means that the code doesn't trigger GstObject and GstElement "constructed" implementations. In particular both GstElement's and GstObject's classes in "constructed" may sign up this object for tracing and GstObject's class sets GST_OBJECT_FLAG_CONSTRUCTED flag. If we don't chain up none of this is going to be executed. For example, before the fix leaks tracer couldn't detect this leak: ```c int main (int argc, char **argv) { g_setenv ("GST_TRACERS", "leaks(name=all-leaks)", TRUE); g_setenv ("GST_DEBUG", "GST_TRACER:7", TRUE); g_setenv ("G_DEBUG", "fatal-warnings", TRUE); gst_init (&argc, &argv); // leak audiomixer: doesn't detect because it's based on the aggregator gst_element_factory_make ("audiomixer", "Jerry"); // leak videoconvert: this one is detected fine because it's not // based on the aggregator //gst_element_factory_make ("videoconvert", "Tom"); gst_deinit (); return 0; } // $ cc tst.c $(pkg-config --cflags --libs gstreamer-1.0) -o tst && ./tst ``` Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/8416>		2025-02-10 17:49:28 +00:00
..
gst	aggregator: fix chaining up in GObject "constructed" virtual methods	2025-02-10 17:49:28 +00:00
meson.build	docs: generate hotdoc configs for libraries with our helper script	2025-01-17 20:36:06 +01:00