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 138105 - [mpeg1videoparse] Hangs while decoding everest.m1v
[mpeg1videoparse] Hangs while decoding everest.m1v
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.8.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-25 16:01 UTC by Johan (not receiving bugmail) Dahlin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Johan (not receiving bugmail) Dahlin 2004-03-25 16:01:36 UTC 
Pipeline:

filesrc location="small/everest.m1v" ! mpeg1videoparse ! sink

everest.m1v can be found here:

http://gstreamer.freedesktop.org/data/media/small/everest.m1v
Comment 1 Johan (not receiving bugmail) Dahlin 2004-03-25 16:07:24 UTC 
Pressed Ctrl-C after a few seconds, then it shows this:

mp1videoparse_parse_seq (mp1videoparse=0x993cc20, buf=0x97cebd4)
    at gstmp1videoparse.c:168
168       gfloat asr_table[] = { 0., 1.,
(gdb) bt

+ Trace 45417

  • #0 mp1videoparse_parse_seq
    at gstmp1videoparse.c line 168
  • #1 mp1videoparse_valid_sync
    at gstmp1videoparse.c line 226
  • #2 gst_mp1videoparse_real_chain
    at gstmp1videoparse.c line 385
  • #3 gst_mp1videoparse_chain
    at gstmp1videoparse.c line 312
  • #4 gst_opt_scheduler_chain_wrapper
    at gstoptimalscheduler.c line 1325 

(gdb) info locals
width = -1075318080
height = 8968532
asr_idx = 4
fps_idx = 7
asr_table = {0, 1, 0.673500001, 0.703100026, 0.761500001, 0.805499971,
  0.843699992, 0.89349997, 3.79751884e-43, 0, 1.3679414e-38, 3.04442825e-33,
  3.04447086e-33, 5.73831721e-42, -1.81210423}
fps_table = {3.04447086e-33, 3.04442825e-33, -1.81209278, 1.34179303e-38,
  3.03200988e-33, 7.00649232e-45, 1.3679236e-38, 1.36794546e-38,
  3.79751884e-43}

Doesn't seem to make much sense though, since pressing Ctrl-C randomly shows
different places (data pushing, thread locking, data chaining, demuxing etc)
Comment 2 Ronald Bultje 2004-04-10 22:41:06 UTC 
Fixed in CVS.