GNOME Bugzilla – Bug 637824
mpeg4videoparse: gst_buffer_is_metadata_writable warning (regression)
Last modified: 2011-01-05 17:08:14 UTC
This is a regression from the latest release The message output on the terminal... (DigitalObservation:8730): GStreamer-WARNING **: (gstbuffer.c:495):gst_buffer_set_caps: runtime check failed: (gst_buffer_is_metadata_writable (buffer)) Backtrace...
+ Trace 225223
This should fix it. Please re-open if not: commit e29a1073b1bceb0c279c0a96c233d11d211f97ac Author: Tim-Philipp Müller <tim.muller@collabora.co.uk> Date: Wed Dec 22 21:44:47 2010 +0000 mpeg4videoparse: ensure buffer metadata is writable before modifying it https://bugzilla.gnome.org/show_bug.cgi?id=637824
No such luck. I just git updated all packages, built and installed on my test system... same messages.
> No such luck. I just git updated all packages, built and installed on my test > system... same messages. This means it's not fixed then? (VERIFIED = you confirm it's been fixed) Same stack trace still?
I just had no idea what to change it to to "reopen it".. I don't have a stack trace comparison. I just ran it and the same messages appeared after the same behaviour. I can do a stack trace comparison if you need it.... Feel free to change status to whatever you want to mean "Open and unfixed"
(In reply to comment #4) > I just had no idea what to change it to to "reopen it".. I don't have a stack > trace comparison. I just ran it and the same messages appeared after the same > behaviour. I can do a stack trace comparison if you need it.... Feel free to > change status to whatever you want to mean "Open and unfixed" Ok, well could you just get another stack trace with the up-to-date mpeg4videoparse from git? (Run in gdb with G_DEBUG=fatal_warnings gdb ...)
No idea why the installed debuginfo for mpeg4videoparse isn't being detected... so I'm not sure if this BT is even useful to you...
+ Trace 225231
(In reply to comment #6) > No idea why the installed debuginfo for mpeg4videoparse isn't being detected... > so I'm not sure if this BT is even useful to you... Luckily there's only one gst_buffer_set_caps() call... Let's try this: commit e6d0435a8ed722ba1d61b1c2d56a26c1b6fc5ff8 Author: Tim-Philipp Müller <tim.muller@collabora.co.uk> Date: Thu Dec 23 22:01:00 2010 +0000 mpeg4videoparse: try harder to make buffer metadata writable before modifying Also, check buffer for NULL-ness before dereferencing it. https://bugzilla.gnome.org/show_bug.cgi?id=637824 Does it work fine now?
It does now.
Thanks for confirming.
I should note that my first test was a no-op as I hadn't actually updated the mpeg4videoparse, so whatever changes you made the first time probably did it. Did you want me to check the original commit? Or are the two combined changes sufficient?
If it works now, it's all good, thanks.