[Bug 667352] New: [0.11] misc core API/bug comments/nitpicks

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=667352
  GStreamer | gstreamer (core) | 0.11.x

           Summary: [0.11] misc core API/bug comments/nitpicks
    Classification: Platform
           Product: GStreamer
           Version: 0.11.x
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: mnauw at users.sourceforge.net
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Collecting a number of odd things/behaviour that pop up when browsing 0.11
core; maybe they are bugs, maybe as it is supposed to be.

* memory/buffer:
- no checking on modifying size in _unmap
- a number of operations on _buffer can be tricky with an outstanding _map
(notable removing a memory range, or performing another _map); no checking
though
- what is to happen upon release/free with an outstanding _map (allowed or not,
automagic stuff ?); no doc or sanity checking
- some adapter operations with outstanding _map can be likewise tricky (most
notably another _map, _flush or _clear); see also bug #664133.

* (sticky) event:
- order of serialized events not preserved;
a sticky event could be received, not sent downstream and stored, and then a
subsequent event is sent directly downstream without sending the stored first
* a FLUSH_STOP does not clear any sticky event, so the latter can turn up after
a flush, which seems to be very (too?) sticky
* when a sticky event is stored, it replaces the currently stored of same type,
and as such it will also be sent in order of the "old event", rather than
current/new order

-- 
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.