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 676633 - seeking fails
seeking fails
Status: RESOLVED DUPLICATE of bug 671776
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-23 12:31 UTC by Andreas Frisch
Modified: 2012-05-25 05:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case. syntax: reverseseektest uri rate1 rate2 (7.66 KB, text/x-csrc)
2012-05-23 12:31 UTC, Andreas Frisch 		Details

Description Andreas Frisch 2012-05-23 12:31:41 UTC 
Created attachment 214750 [details]
test case. syntax: reverseseektest uri rate1 rate2

with my little example application when running with any mkv file

./reverseseektest64 file:///net/media/Videos/Trickfilme/Toy\ Story\ 3.mkv 2 -2

****************do_seek::initial 0 gst_element_query_position = 0:04:18.299750000 rate = 2,000000 (len=1:43:03.606000000)

(reverseseektest64:12649): GStreamer-WARNING **: wrong STREAM_LOCK count 0 for lock 0xe06240 on task 0xe460c0
do_seek::seek rate 2,000000 command returned 1. new gst_element_query_position = 0:04:18.299750000

same thing happens with the scrubby seek example and any rate:

(lt-scrubby:12824): GStreamer-WARNING **: wrong STREAM_LOCK count 0 for lock 0x25359c0 on task 0x2571090

i'm using current git versions of core, base + bad branch 0.10

glib version is 2.32.1-3

with glib version 2.30.3 and release 0.10.36 my testcase will crash on the dreambox:

GThread-ERROR **: file gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
Trace/breakpoint trap
Comment 1 Vincent Penquerc'h 2012-05-23 14:21:36 UTC 
Looks like https://bugzilla.gnome.org/show_bug.cgi?id=661914, though your version seems new enough (not sure which version of glib would have that fix first).
Comment 2 Vincent Penquerc'h 2012-05-24 10:51:08 UTC 
May also be already fixed by https://bugzilla.gnome.org/show_bug.cgi?id=671776 (both that and the glib issue would cause this STREAM_LOCK message).

Setting to NEEDINFO to wait till these two things are tested with.
Comment 3 Andreas Frisch 2012-05-25 05:50:41 UTC 
It turns out, the glib fix doesn't apply in my situation, because my glib version is actually older that the rewrite which introduced the bug.

Vincent: thank you for your suggestion and your patch ee1be9236f9874ddb54345888be791ccee0f8a3a which fixed this crash.

*** This bug has been marked as a duplicate of bug 671776 ***