totem-video-thumbnailer crashed with SIGSEGV in calloc()

[Danny]

Binary package hint: totem

Totem suddenly closes just after I'm trying to open a .mkv file.

ProblemType: Crash
Architecture: i386
Date: Thu Oct 15 22:30:09 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/totem-video-thumbnailer
Package: totem 2.28.1-0ubuntu4
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 file:///home/username/Pulpit/School%20Rumble%201%20-%2001.mkv /tmp/.gnome_desktop_thumbnail.YLU41U
ProcEnviron:
 LANGUAGE=pl_PL.UTF-8
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x2910448: mov %edx,0x8(%ecx)
 PC (0x02910448) ok
 source "%edx" ok
 destination "0x8(%ecx)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 calloc () from /lib/tls/i686/cmov/libc.so.6
 g_malloc0 () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: totem-video-thumbnailer crashed with SIGSEGV in calloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

StacktraceTop:_int_malloc (av=<value optimized out>, bytes=<value optimized out>)
__libc_calloc (n=1, elem_size=40) at malloc.c:4041
g_malloc0 () from /lib/libglib-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Danny (dparzniewski)]

Hi, the problem exist only with .mkv files. It occur on Ubuntu 9.10 upgraded from 9.04 and on Ubuntu 9.10 installed at formatted harddisk.

[Pedro Villavicencio (pedro)]

could you please install the libglib, libgtk and totem debugging symbols and get another log if you still managed to reproduce the problem?

[CassieMoondust (cassie-lx)]

totem-video-thumbnailer crashed during copy of a dv camcorder file from one hard disk to another (18GB). Nautilus stops copy this file and totem and totem-video-thumbnailer doesn't respond anymore. I cannot kill them with kill or killall. Only a reboot stops them (why i cannot kill them as root?!?)

This message appears many times in the kern.log:
Jan 24 01:31:52 kernel: [ 1800.890086] INFO: task totem-video-thu:3492 blocked for more than 120 seconds.
Jan 24 01:31:52 kernel: [ 1800.890094] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 24 01:31:52 kernel: [ 1800.890101] totem-video-t D 00000000ffffffff 0 3492 3491 0x00000004
Jan 24 01:31:52 kernel: [ 1800.890112] ffff88005e54fe58 0000000000000086 ffffea00027c9738 0000000000015880
Jan 24 01:31:52 kernel: [ 1800.890122] ffff8801a5fcb110 0000000000015880 0000000000015880 0000000000015880
Jan 24 01:31:52 kernel: [ 1800.890130] 0000000000015880 ffff8801a5fcb110 0000000000015880 0000000000015880
Jan 24 01:31:52 kernel: [ 1800.890139] Call Trace:
Jan 24 01:31:52 kernel: [ 1800.890156] [<ffffffff81528847>] __mutex_lock_slowpath+0xd7/0x160
Jan 24 01:31:52 kernel: [ 1800.890168] [<ffffffff81036419>] ? default_spin_lock_flags+0x9/0x10
Jan 24 01:31:52 kernel: [ 1800.890177] [<ffffffff81528746>] mutex_lock+0x26/0x50
Jan 24 01:31:52 kernel: [ 1800.890187] [<ffffffff8111f571>] generic_file_llseek+0x31/0x70
Jan 24 01:31:52 kernel: [ 1800.890195] [<ffffffff8111ed85>] vfs_llseek+0x35/0x40
Jan 24 01:31:52 kernel: [ 1800.890203] [<ffffffff8111f9ee>] sys_lseek+0x5e/0x80
Jan 24 01:31:52 kernel: [ 1800.890212] [<ffffffff81012002>] system_call_fastpath+0x16/0x1b

[Omer Akram (om26er)]

this issue should be fixed in Ubuntu-.10.04 and 10.10 could you please confirm?

[Omer Akram (om26er)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.