GNOME Bugzilla – Bug 138635
two GLib-GObject-CRITICAL Messages when running gst-register-0.8 with a certain LADSPA plugin
Last modified: 2004-12-22 21:47:04 UTC
* install the LADSPA plugin from http://www.tux.org/pub/tux/ladspa/alienwah-1.11.tar.gz * rerun gst-register ... (process:20495): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846 (g_param_spec_float): assertion `default_value >= minimum && default_value <= maximum' failed (process:20495): GLib-GObject-CRITICAL **: file gobject.c: line 275 (g_object_class_install_property): assertion `G_IS_PARAM_SPEC (pspec)' failed * running with gdb and --gst-fatal-warnings the backtrace is
+ Trace 45558
gst-compprep-0.8 is triggering that too. (process:21602): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846 (g_param_spec_float): assertion `default_value >= minimum && default_value <= maximum' failed (process:21602): GLib-GObject-CRITICAL **: file gobject.c: line 275 (g_object_class_install_property): assertion `G_IS_PARAM_SPEC (pspec)' failed (process:21602): GLib-GObject-CRITICAL **: file gparamspecs.c: line 1846 (g_param_spec_float): assertion `default_value >= minimum && default_value <= maximum' failed ** (process:21602): CRITICAL **: file dparammanager.c: line 618 (gst_dpman_new_wrapper): assertion `param_spec != NULL' failed ** (process:21602): CRITICAL **: file dparammanager.c: line 234 (gst_dpman_add_required_dparam_direct): assertion `dpwrap != NULL' failed ** (process:21602): WARNING **: 0 sink pads, 2 src pads not yet supported
Created attachment 26362 [details] [review] checks and corrects ladspa parameter bounds, before using them as g_param_specs when initialising a g_param_spec with wrong values, the user will get a glib critical message, this prevents it from happening [in this case ;-)]. I notified the original ladspa plugin author to fix it as well.
applied.