GNOME Bugzilla – Bug 796806
Problems deserializing stream-start events
Last modified: 2018-11-03 12:47:30 UTC
> 0:00:07.399046676 12893 0x7f6d700040a0 DEBUG rtpgstdepay gstrtpgstdepay.c:290:read_event:<depayloader> parsing event GstEventStreamStart, stream-id=(string)d9486e4ba1afa28e746e6a227057a1bbffd29ae47871dbe2c22d900098420579, flags=(GstStreamFlags)GST_STREAM_FLAG_NONE, group-id=(uint)7, stream=(GstStream)"\(GstStream\)\ stream0"; > 0:00:07.399060467 12893 0x7f6d700040a0 WARN structure gststructure.c:1974:gst_structure_parse_field: failed to parse value stream=(GstStream)(GstStream) stream0eam0"; > 0:00:07.399073720 12893 0x7f6d700040a0 WARN structure gststructure.c:2042:priv_gst_structure_parse_fields: Failed to parse field, r=stream=(GstStream)(GstStream) stream0eam0"; There are multiple problems here: a) There's the stream in here now, which is not serializable. In older versions of GStreamer this was not a problem and as such it's arguably a backwards compatibility breakage Not sure what we can do about that, other than letting deserialization skip over fields that it can't deserialize... which might have other problems if they are fields that are actually expected to be there (and then other code dereferences a NULL later) b) Trying to deserialize the stream field just completely falls apart, not sure what the parsing code tries to do there at all. This might also affect other structures
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/304.