[FFmpeg-trac] #506(undetermined:new): FFMPEG32 Windows Build CRASH

[FFmpeg]

#506: FFMPEG32 Windows Build CRASH
-------------------------------------+-------------------------------------
             Reporter:               |                    Owner:  michael
  plaguebreath                       |                   Status:  new
                 Type:  defect       |                Component:
             Priority:  normal       |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Does the crash only happen for -ss 1394? If a smaller value is sufficient,
 it should be easy to cut the sample (but I suspect it can also be cut
 significantly to still get 1394 seconds).
 Is the pad filter necessary to reproduce the crash?
 Is -s 800x600 necessary to reproduce the crash or does it also crash for
 the original resolution?
 Is -sameq necessary?
 (-vcodec mjpeg and -f rawvideo should be unneeded)

 Is the crash also reproducible without encoding?
 ffmpeg -ss 1394 -i "C:\testing\1.wmv" -an -s 800x600 -vf
 pad=800:600:0:0:black -f null -

 Please provide a minimal command line (that is a short command line that
 does include -an).

-- 
Ticket URL: <https://avcodec.org/trac/ffmpeg/ticket/506#comment:3>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker