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 386909 - [ffdec_h264] crash watching diggnation episode
[ffdec_h264] crash watching diggnation episode
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
0.10.x
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 388120 390069 395418 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-17 19:33 UTC by Justin
Modified: 2011-06-28 23:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Ubuntu Crash Report (50.18 KB, application/octet-stream)
2006-12-20 22:27 UTC, Justin
Details
Debug Log (939.75 KB, application/x-7z-compressed)
2007-08-14 16:51 UTC, Justin
Details

Description Justin 2006-12-17 19:33:33 UTC
Version: 2.16.2

What were you doing when the application crashed?
I was watching an episode of Diggnation (large H.264) when it suddenly crashed.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 205754368 vsize: 0 resident: 205754368 share: 0 rss: 70447104 rss_rlim: 0
CPU usage: start_time: 1166383953 rtime: 0 utime: 490 stime: 0 cutime:466 cstime: 0 timeout: 24 it_real_value: 0 frequency: 8

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226127696 (LWP 12661)]
[New Thread -1363711072 (LWP 12674)]
[New Thread -1349764192 (LWP 12673)]
[New Thread -1341277280 (LWP 12672)]
[New Thread -1332479072 (LWP 12671)]
[New Thread -1310266464 (LWP 12669)]
[New Thread -1292248160 (LWP 12668)]
[New Thread -1277600864 (LWP 12665)]
[New Thread -1269130336 (LWP 12664)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 6 (Thread -1310266464 (LWP 12669))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 __assert_fail
    from /lib/tls/i686/cmov/libc.so.6
  • #8 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #9 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #10 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #11 avcodec_decode_video
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #12 gst_ffmpegdec_register
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #13 gst_ffmpegdec_register
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #14 gst_pad_alloc_buffer
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 gst_queue_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #17 gst_task_set_lock
    from /usr/lib/libgstreamer-0.10.so.0
  • #18 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #19 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #20 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #21 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 palfrey 2006-12-17 21:04:08 UTC
gstreamer issue, reassigning

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Justin 2006-12-17 23:15:13 UTC
OK, is this any better?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 208658432 vsize: 0 resident: 208658432 share: 0 rss: 72859648 rss_rlim: 0
CPU usage: start_time: 1166397046 rtime: 0 utime: 528 stime: 0 cutime:500 cstime: 0 timeout: 28 it_real_value: 0 frequency: 12

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226021200 (LWP 18974)]
[New Thread -1359135840 (LWP 18987)]
[New Thread -1350743136 (LWP 18986)]
[New Thread -1342256224 (LWP 18985)]
[New Thread -1333392480 (LWP 18984)]
[New Thread -1311179872 (LWP 18982)]
[New Thread -1293161568 (LWP 18981)]
[New Thread -1277494368 (LWP 18978)]
[New Thread -1269023840 (LWP 18977)]
0xffffe410 in __kernel_vsyscall ()

Thread 6 (Thread -1311179872 (LWP 18982))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 __assert_fail
    from /lib/tls/i686/cmov/libc.so.6
  • #8 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #9 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #10 ff_h261_reorder_mb_index
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #11 avcodec_decode_video
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #12 gst_ffmpegdec_register
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #13 gst_ffmpegdec_register
    from /usr/lib/gstreamer-0.10/libgstffmpeg.so
  • #14 gst_pad_alloc_buffer
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 gst_queue_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #17 gst_task_set_lock
    from /usr/lib/libgstreamer-0.10.so.0
  • #18 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #19 g_thread_create_proxy
    at gthread.c line 553
  • #20 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #21 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 3 palfrey 2006-12-19 15:08:14 UTC
The problem appears to be buried somewhere in the middle of the ffmpeg module. If you were running feisty, this would be a bit easier. As it is, I *can* give you a procedure that should work, but I would advise against doing this unless you really know what you're doing with apt-get. Effectively what this will try and do is only upgrade the gstreamer ffmpeg module to the feisty version and see if you can reproduce this still.

If you're sure, do the following. Add

deb http://archive.ubuntu.com/ubuntu/ feisty main restricted universe
deb http://people.ubuntu.com/~pitti/ddebs feisty main universe

to your /etc/apt/sources.list and then install gstreamer0.10-ffmpeg-dbgsym. This *may* try and pull in various other dependancies, and you're going to have to use your best judgement here to avoid having your entire setup upgraded to feisty.

You might now not be able to reproduce the bug, in which case we can close this as fixed in the later version. Otherwise, you should now be able to get a better stacktrace.

Oh, and after you've done all of that, I would advise removing the two added lines from your /etc/apt/sources.list again.
Comment 4 Justin 2006-12-20 02:40:47 UTC
All right, I bit the bullet and just upgraded to Feisty completely (which has a few improvements that was worth the upgrade anyway). I can still get Totem to crash, but Bug Buddy doesn't come up when I do this now.

To reproduce, I just open up episode 76 of diggnation (the large H.264) and seek through towards the end quickly. The video window turns grey for a brief moment, then it crashes.

Anyhow, is there another way to get that backtrace?
Comment 5 palfrey 2006-12-20 10:41:18 UTC
(In reply to comment #4)
> Anyhow, is there another way to get that backtrace?

Yes. See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running

Comment 6 Justin 2006-12-20 22:27:05 UTC
Created attachment 78721 [details]
Ubuntu Crash Report
Comment 7 Justin 2006-12-20 22:29:10 UTC
I was able to crash it again, but this time the Ubuntu crash program opened up. I've attached the smaller file it produced here (the large one was 13 MB, too large to upload).
Comment 8 Bruno Boaventura 2006-12-21 15:35:15 UTC
*** Bug 388120 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2007-01-12 03:52:22 UTC
*** Bug 390069 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2007-01-12 03:52:34 UTC
*** Bug 395418 has been marked as a duplicate of this bug. ***
Comment 11 Edward Hervey 2007-08-14 15:01:16 UTC
This is weird, the first backtraces shows... that it's using h261 ? (does that even exist ?).

Justin, could you provide a debug log that would help us better figure out what's wrong ?

# GST_DEBUG=3,ffmpeg:5 totem yourfile.name > log 2>&1
[wait for it to crash]
# bzip2 log

And then attach log.bz2 to this bug report.
Comment 12 Justin 2007-08-14 16:51:45 UTC
Created attachment 93654 [details]
Debug Log
Comment 13 Justin 2007-08-14 16:55:58 UTC
I hope that helps. The Bziped one was over 1 MB, so I couldn't attach it. I used 7-zip instead, which compressed it better.
Comment 14 Wim Taymans 2008-01-22 12:24:24 UTC
it's not syncing correctly after a seek, making ffmpeg crash.
Comment 15 David Hoyt 2009-12-14 19:33:24 UTC
Is this issue still unresolved? We're seeing it appear with the latest source using the following pipeline:

videotestsrc ! ffmpegcolorspace ! x264enc bitrate=300 ! rtph264pay ! rtph264depay ! ffdec_h264 ! ffmpegcolorspace ! autovideosink
Comment 16 David Hoyt 2009-12-14 19:34:07 UTC
Forgot to mention that we're running this on Windows XP.
Comment 17 Sebastian Dröge (slomo) 2011-05-18 12:32:55 UTC
That pipeline works fine for me with latest GIT. Does it work for you too now? If not, could you get a new backtrace?
Comment 18 Fabio Durán Verdugo 2011-06-28 23:33:59 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!