#335 closed defect (fixed)
Quicktime movie causes MPlaer to crash
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Component: | core |
| Version: | 1.0pre7 | Severity: | critical |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Reproduced by developer: | no | Analyzed by developer: | no |
Description
Running Debian. Loading the .MOV file at the attached URL causes MPlayer to crash:
# mplayer brig_qtvr.MOV
MPlayer 1.0pre7-3.3.5 (C) 2000-2005 MPlayer Team
CPU: Intel Pentium 4/Xeon/Celeron Foster (Family: 8, Stepping: 4)
Detected cache-line size is 64 bytes
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for Debian.
73 audio & 180 video codecs
Opening joystick device /dev/input/js0
Can't open joystick device /dev/input/js0 : No such device
Can't init input joystick
Setting up LIRC support...
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support.
You will not be able to use your remote control.
Playing brig_qtvr.MOV.
Cache fill: 6.25% (65536 bytes) QuickTime/MOV file format detected.
MOV track #0: 1 chunks, 0 samples
Generic track - not completely understood! (id: 0)
MOV track #1: 1 chunks, 0 samples
Generic track - not completely understood! (id: 1)
MOV track #2: 6 chunks, 6 samples
MOV: Found unsupported Gamma-Correction movie atom (12)!
Image size: 512 x 512 (24 bpp)
Display size: 320 x 240
Fourcc: jpeg Codec: 'Foto - JPEG'
MOV track #3: 0 chunks, 0 samples
* constant samplesize & variable duration not yet supported! *
Contact the author if you have such sample file!
MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug.
Fixed, though the video is not really worth watching (just 6 jpeg frames *g*)