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 753442 - matroskademux: may get stuck when demuxing forced pgs subtitles
matroskademux: may get stuck when demuxing forced pgs subtitles
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-10 10:29 UTC by Andreas Frisch
Modified: 2015-08-10 10:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas Frisch 2015-08-10 10:29:35 UTC
with this little modification:
-  subcaps = gst_caps_from_string ("text/x-pango-markup; text/plain");
+  subcaps = gst_caps_from_string ("text/x-pango-markup; text/plain; subpicture/x-pgs");
the playbin-text.c example can be used as a testcase for this issue.

after the nth (in my case 6th) subtitle, playback stalls:

** Message: received a subtitle at position 0:19:31.755000000, running_time 0:19:31.756610000
00000000 (0x7f61c956d400): 16 00 0b 07 80 04 38 10 00 05 00 00 00 00 17 00  ......8.........
00000010 (0x7f61c956d410): 0a 01 00 03 50 03 63 00 e3 00 32 80 00 00        ....P.c...2...  
^C

* 1    Thread 0x7f61d5691700 (LWP 5202) "playbin-text" 0x00007f61d3d244ed in poll () from /usr/lib/libc.so.6
(gdb) bt full
  • #0 poll
    from /usr/lib/libc.so.6
  • #1 ??
    from /usr/lib/libglib-2.0.so.0
  • #2 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #3 main
    at playbin-text.c line 168


testfile available at http://dreambox.guru/test_stuck.mkv.xz
Comment 1 Sebastian Dröge (slomo) 2015-08-10 10:37:37 UTC
Can you provide a backtrace of all threads when it gets stuck? The main thread is useless :)
Comment 2 Sebastian Dröge (slomo) 2015-08-10 10:42:36 UTC
As this bug is about 0.10 and 0.10 is no longer supported, I'll close it. If you can reproduce the same problem with 1.4+ please reopen :)