totem assert failure: totem: malloc.c:4591: _int_malloc: Assertion `(unsigned long)(size) >= (unsigned long)(nb)' failed.

[Cloud]

Was streaming video over ssh connection when totem crashed. Worked in vlc but had to wait for it to load. May be due to totem wanting to play information it doesn't currently have.

ProblemType: Crash
Architecture: i386
AssertionMessage: totem: malloc.c:4591: _int_malloc: Assertion `(unsigned long)(size) >= (unsigned long)(nb)' failed.
CrashCounter: 1
Date: Mon Nov 2 17:19:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/totem
NonfreeKernelModules: nvidia
Package: libgstreamer0.10-0 0.10.25-2
ProcCmdline: totem /home/username/.gvfs/sftp\ for\ athrun\ on\ athrun.myftp.org/storage/Videos/Blue\ Submarine\ No.6/01\ -\ Blues.mkv
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: gstreamer0.10
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: totem assert failure: totem: malloc.c:4591: _int_malloc: Assertion `(unsigned long)(size) >= (unsigned long)(nb)' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[steubens (steubens)]

this was happening to me when I loaded some particular .sub subtitles; totem was crashing right off because of my load-sub-on-file load prefs, the stack was all over through separate runs; its running into the weeds in gstreamer

[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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.