[Bug 750397] CRITICAL: Race condition in GstBus

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=750397

--- Comment #17 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Matt Gruenke from comment #16)
> (In reply to Matt Gruenke from comment #13)
> > 
> > I've got a large amount of runtime, on the fix I mentioned in comment #9.
> 
> I forgot to mention that I'm not using any additional mutex or locking
> (contrary to the last paragraph of that comment).  I've only tested this on
> Linux.

If I understand your proposed change correctly, you can still run into the
first situation I mentioned in the commit message.

And AFAIU the blocking mode of the sockets is necessary so that we can be sure
that always either 1 or 0 bytes are in the socket. If you would do a
non-blocking read, you could end up reading nothing, then having 1 byte
arriving in the socket shortly after, and then be in an inconsistent state
again where next time a second byte is written to the socket.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.