[gstreamer-bugs] [Bug 148721] New: - entrygthread fail on SMP systems

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=148721
GStreamer | gstreamer (core) | Ver: 0.8.4

           Summary: entrygthread fail on SMP systems
           Product: GStreamer
           Version: 0.8.4
          Platform: Other
        OS/Version: SunOS
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: sc5 at hermes.usherb.ca
         QAContact: gstreamer-bugs at lists.sourceforge.net


Running gstreamer-0.8.4 on an Sun system (2 Sparc processors running SunOS 5.8),
gst-launch fails with the following assert:

   ** ERROR **: file entryscheduler.c: line 405
(gst_entry_scheduler_get_wrapper): assertion failed: (PAD_PRIVATE (pad)->bufpen
== NULL)

The problem doesn't happen very often.  To reproduce it, I call gst-launch many
times with pipelines such as this one:

  wavenc name=sink ! filesink location="test.wav" { filesrc location="input.mp3"
! spider ! audioconvert ! queue block_timeout=100000 max-size-time=0
max-size-buffers=0 max-size-bytes=0 } !sink.sink

To me, it looks like gst_entry_scheduler_iterate() is called and it schedules
the gst_entry_scheduler_get_wrapper() from the queue, which runs in a different
thread. Before this functions gets to complete, gst_entry_scheduler_iterate() is
called again from the main thread and schedules the same link.

I could be wrong, but I think that when a link is selected for scheduling, it
should be removed from the can_schedulle() list before being run. This would
make sure it won't be called again before it completes.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.