vlc crashed with SIGSEGV in swScale_MMX()

[christian arvai]

Binary package hint: vlc

vlc playing flv. files and crash after 10 min.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/vlc
NonfreeKernelModules: nvidia
Package: vlc-nox 0.9.3-0ubuntu1
ProcAttrCurrent: unusernameonfined
ProcCmdline: vlusername /media/EXTERN\ 2/Musiusername\ Vidio/Dragonforusernamee/DragonForusernamee_-_Through_the_Fire_and_Flames.flv
ProcEnviron:
 PATH=/usr/lousernameal/sbin:/usr/lousernameal/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: vlc
Stacktrace:
 #0 0xausernameddedbd in ?? () from /usr/lib/i686/usernamemov/libswsusernameale.so.0
 #1 0x10101010 in ?? ()
 Bausernamektrausernamee stopped: previous frame inner to this frame (usernameorrupt stausernamek?)
StacktraceTop:
 ?? () from /usr/lib/i686/usernamemov/libswsusernameale.so.0
 ?? ()
Title: vlc crashed with SIGSEGV
Uname: Linux 2.6.27-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:swScale_MMX (c=0x9677ab0, src=0xaeb7903c, srcStride=0xaeb7900c, srcSliceY=0, srcSliceH=256,
sws_scale (c=0x9677ab0, src=0xaeb790c0, srcStride=0xaeb790b4, srcSliceY=0, srcSliceH=256,
Convert (ctx=0x9677ab0, p_dst=0x94362d0, p_src=0x9681cc8, i_height=256, i_plane_start=0,
Filter (p_filter=0x95d497c, p_pic=0x9565e8c) at swscale.c:542
vout_RenderPicture (p_vout=0x956533c, p_pic=0x95656ac, p_subpic=0x0)

[quazgar (quazgar)]

This could be possibly related to https://roundup.ffmpeg.org/roundup/ffmpeg/issue811

[Hew (hew)]

There have been a large number of bugfixes with the latest VLC release, 1.0.1-1ubuntu1. Can you reproduce your issue with this latest version? You can test this in Ubuntu Karmic, or Ubuntu Jaunty with the MOTU Media PPA at https://launchpad.net/~motumedia/+archive/ppa . Thanks in advance.

[Benjamin Drung (bdrung)]

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!