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 397942 - crash in Movie Player: i tried to open a movie....
crash in Movie Player: i tried to open a movie....
Status: RESOLVED DUPLICATE of bug 357002
Product: totem
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-01-18 10:16 UTC by ch05100
Modified: 2007-01-18 20:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ch05100 2007-01-18 10:16:44 UTC 
Version: 2.16.2

What were you doing when the application crashed?
i tried to open a movie. all the others worked, but this specific movie is one file of 1,4GB, so i guess that made the difference.


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

Memory status: size: 115318784 vsize: 0 resident: 115318784 share: 0 rss: 28966912 rss_rlim: 0
CPU usage: start_time: 1169115282 rtime: 0 utime: 84 stime: 0 cutime:79 cstime: 0 timeout: 5 it_real_value: 0 frequency: 4

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 -1225910608 (LWP 27656)]
[New Thread -1305003104 (LWP 27670)]
[New Thread -1296356448 (LWP 27669)]
[New Thread -1284359264 (LWP 27668)]
[New Thread -1269744736 (LWP 27663)]
[New Thread -1261274208 (LWP 27662)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103201

Thread 4 (Thread -1284359264 (LWP 27668))

  • #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 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_malloc
    from /usr/lib/libglib-2.0.so.0
  • #10 gst_buffer_new_and_alloc
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 gst_file_src_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #12 gst_base_src_get_type
    from /usr/lib/libgstbase-0.10.so.0
  • #13 gst_base_src_get_type
    from /usr/lib/libgstbase-0.10.so.0
  • #14 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 _gst_format_initialize
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #18 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #19 gst_type_find_element_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #20 gst_pad_get_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #21 gst_pad_pull_range
    from /usr/lib/libgstreamer-0.10.so.0
  • #22 gst_riff_read_chunk
    from /usr/lib/libgstriff-0.10.so.0
  • #23 gst_avi_demux_get_type
    from /usr/lib/gstreamer-0.10/libgstavi.so
  • #24 gst_avi_demux_get_type
    from /usr/lib/gstreamer-0.10/libgstavi.so
  • #25 gst_avi_demux_get_type
    from /usr/lib/gstreamer-0.10/libgstavi.so
  • #26 gst_task_set_lock
    from /usr/lib/libgstreamer-0.10.so.0
  • #27 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #28 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #29 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #30 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


Jens Granseuer





          2007-01-18 20:45:52 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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