After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 163101 - [videomixer] Segmentation fault in videomixer plugin
[videomixer] Segmentation fault in videomixer plugin
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-06 08:37 UTC by tommydal
Modified: 2005-11-21 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description tommydal 2005-01-06 08:37:52 UTC 
The following pipeline:

gst-launch videotestsrc ! ffmpegcolorspace ! videomixer ! ffmpegcolorspace !
xvimagesink

causes a segmentation fault. The reason for this is that the width, height and
framerate parameters are set incorrectly for the videomixer pads during
negotiation. (Running it at debug level 5 shows this clearly)

Changing the caps template for framerate, width and height in videomixer from a
range to a int results in this pipeline working correctly.
Comment 1 Stephane Loeuillet 2005-01-06 10:28:04 UTC 
no segfault for me with this pipeline but the window stays definitively black/empty.

using CVS of everything
Comment 2 Ronald Bultje 2005-02-08 19:07:12 UTC 
The reason that you don´t see it is because your PCU doesn´t SIGFPE on FP-0. The
framerate is indeed zero. Videomixer does not do bidirectional capsnego, which
is a videomixer bug.
Comment 3 Ronald Bultje 2005-02-08 19:51:57 UTC 
On closer look, I don´t think you can use videomixer without filtercaps. Ask its
author if you need that feature...
Comment 4 Wim Taymans 2005-11-21 19:49:20 UTC 
Works fine in HEAD now.