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 112086 - [threads] GStreamer needs working threading
[threads] GStreamer needs working threading
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal critical
: 0.9.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 111146
 
 
Reported: 2003-05-02 16:03 UTC by Benjamin Otte (Company)
Modified: 2005-07-14 14:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin Otte (Company) 2003-05-02 16:03:39 UTC
gst-launch { priority=3 fakesrc num-buffers=1 ! fakesink }

will probably run into a trace/breakpoint trap.
In my gdb it locks forever.
On some rare occasisons it might even work.
On the multi-CPU Solaris machine it's doing some weird mad stuff I don't
even understand.

I'm opening this as bug, because I want to have a general consensus on how
we handle access to members of different objects. Particularly interesting
are element->current_state and element->pending_state for this case.

I'd propose to clearly define who may read/write to each member of each
element or which lock is needed to access it.
Comment 1 Christian Fredrik Kalager Schaller 2005-02-10 18:19:54 UTC
Should this bug report be closed as wontfix Benjamin? As the threading issues
will not be fixed in 0.8 anyway. Its already fixed in Wim's branch and I assume
it was not a problem in your branch either.
Comment 2 Benjamin Otte (Company) 2005-02-13 13:55:12 UTC
I'd prefer if those bugs were left open until we have a 0.9 branch that has
solved the particular issue.
Comment 3 Ronald Bultje 2005-02-14 09:21:49 UTC
I agree with Benjamin.
Comment 4 Andy Wingo 2005-07-14 14:53:17 UTC
Pipeline from original report works in HEAD (and has for a while), closing as FIXED.