GNOME Bugzilla – Bug 790854
assertion 'qdata->size == sizeof (gint64)' failed
Last modified: 2018-01-13 12:27:49 UTC
Hello, i built gmrender-resurrect on ubuntu x64. When starting i get 8 Lines of: ** (gmediarender:22787): CRITICAL **: gst_ffmpeg_cfg_set_property: assertion 'qdata->size == sizeof (gint64)' failed and upon connecting a client continuos output of: (gmediarender:22787): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion 'segment->format == format' failed Although the program works i was wondering if i could awoid filling my journal with these errors. Thanks
The first looks like a problem in gst-libav, so moving things there for now. The second one is usually a problem with how the pipeline is constructed, and should probably be reported against gmediarender in the first instance.
alright, thanks. One more thing: i output to a pipe (for snapcast) and do not have a soundcard build in the PC that gmediarender is runnuíng on.
Regarding the qdata->size assert - I have no explanation for this, other than ffmpeg changing the size of the struct member in a newer version (but it doesn't look like that from git master). We'd need more info how to reproduce that. What exact version of ffmpeg is gst-libav built against etc?
Sadly, my skills don't go much beyond cloning and building by following the readme. But i would gladly follow more specific instructions to solve this.
edit: these instructions: https://github.com/hzeller/gmrender-resurrect/blob/master/INSTALL.md
Ok, that sounds like the problem is with a gstreamer1.0-libav that is installed from package. So this would mean the problem is with ubuntu's packaging. Which seems quite unlikely because I'm sure we would have seen plenty of reports about this if that was indeed the case. Another possibility is some random memory corruption caused by some other piece of code, perhaps/probably gmrender. I would say please file a bug against gmrender and see what they come up with. There's currently not much I can do about this, sorry.
I'll close this for now, since there isn't really enough actionable info here, and I can't think of any possible explanations for this right now, sorry. Please re-open if you have more info or the gmrender people have any ideas. If it's a general problem I'm sure someone will run into it again sooner or later :)
Bug #789379 could possibly be related, but it's a bit of a long shot and I wouldn't think that a distro package would be affected.