[MPlayer-users] Mplayer crash when playing RTSP and disconnect

[lonkaji]

Hi, thanks for your answer.

Here is the complete log:

mplayer -loop 0 rtsp://root:pass@192.168.0.127/axis-media/media.amp
MPlayer SVN-r32492-4.5.1 (C) 2000-2010 MPlayer Team
159 audio & 349 video codecs
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 rtsp://root:pass@192.168.0.127/axis-media/media.amp.
Resolving 192.168.0.127 for AF_INET6...

Couldn't resolve name for AF_INET6: 192.168.0.127
Connecting to server 192.168.0.127[192.168.0.127]: 554...

librtsp: server responds: 'RTSP/1.0 401 Unauthorized'
rtsp_session: unsupported RTSP server. Server type is 'unknown'.
STREAM_LIVE555, URL: rtsp://root:pass@192.168.0.127/axis-media/media.amp
Stream not seekable!
 file format detected.
Initiated "video/H264" RTP subsession on port 48304
VIDEO:  [H264]  0x0  0bpp  20.000 fps    0.0 kbps ( 0.0 kbyte/s)
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file: No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Audio: no sound
Starting playback...
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [xv] 640x480 => 640x480 Planar YV12
V:   0.2  67/ 67  5%  0%  0.0% 0 0



MPlayer interrupted by signal 11 in module: free_demuxer
- 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.