[Bug 673991] [0.10] basetransform regression: gstreamer hangs when accessing webcam (on specific hardware)

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=673991
  GStreamer | gstreamer (core) | 0.10.36

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |t.i.m at zen.co.uk
          Component|don't know                  |gstreamer (core)
            Summary|gstreamer hangs when        |[0.10] basetransform
                   |accessing webcam (on        |regression: gstreamer hangs
                   |specific hardware)          |when accessing webcam (on
                   |                            |specific hardware)

--- Comment #3 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-09-29 14:13:31 UTC ---
Response in launchpad bug was: "It never really hung for me. What happened was
that the ubiquity tread used all the CPU it could get and start eating up all
the memory. After almost an hour of unresponsiveness the last bit of memory and
swap was gobbled up and the ubiquity thread was killed (by 'kswap0' or
something with a similar name). After that the liveCD desktop would start. It
does feel like something hangs, but the machine is actually really busy (and
unresponsive). I don't have a backtrace or the bugged .iso to reproduce the
bug, sorry."

Not sure what to do about this.

The commit in question that was reverted downstream is this btw:

 commit f56c6e12255b37d75b1eb949e434fa8e3bb33f51
 Author: Sebastian Dröge <sebastian.droege at collabora.co.uk>
 Date:   Wed May 4 11:29:15 2011 +0200

    basetransform: In getcaps() prefer the caps order and caps of downstream if
possible


It would be useful, to just run it in gdb and then after it has been going at
it for multiple seconds at full CPU just press control-C and get a stack trace
of all threads, so we get a rough idea of where it's doing things.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.