MP4 videos refusing to play in M56, regression from M55 |
||||
Issue descriptionChrome Version : 56.0.2924.87 URLs (if applicable) : https://drive.google.com/open?id=0B4fX4mjfIGmrNGNLYXR1Q2lFd1E Audio/Video format (if applicable): Info dump from `mplayer -v`: VIDEO: [H264] 352x240 24bpp 10.000 fps 242.7 kbps (29.6 kbyte/s) [V] filefmt:44 fourcc:0x34363248 size:352x240 fps:10.000 ftime:=0.1000 Clip info: major_brand: isom minor_version: 512 compatible_brands: isomiso2avc1mp41 encoder: Lavf56.40.101 Special chrome flags (if applicable): None Behavior in Safari (if known): Unknown. Behavior in Firefox (if known): Plays. Behavior in IE: Plays. Video issue, Audio issue, both, neither? Video only; sample has no audio track. <b>Flash or HTML5? <right-clicking most players will either reveal some text</b> with “Flash”; otherwise likely HTML5> HTML5 No crash report; video refuses to play, no thumbnail. What steps will reproduce the problem? (1) Load video file directly with file://... (2) Video controls load, but cannot play video. What is the expected result? Video plays - worked on M55. What is the actual result? Frozen controls, first frame of video is not shown (black screen).
,
Mar 2 2017
+ ligimole@ and bustamante@. woogie@, could you please try to repro this with latest M57 beta (57.0.2987.88)?
,
Mar 2 2017
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x67a240] st: 0 edit list: 1 Missing key frame while searching for timestamp: 0
[h264 @ 0x67bd00] illegal memory management control operation 14
[h264 @ 0x67bd00] Missing reference picture, default is 0
Last message repeated 1 times
[h264 @ 0x67bd00] left block unavailable for requested intra4x4 mode -1
[h264 @ 0x67bd00] error while decoding MB 0 0, bytestream 2511
[h264 @ 0x67bd00] concealing 330 DC, 330 AC, 330 MV errors in P frame
Clip is corrupted so can't guarantee it will play.
,
Mar 2 2017
I was able to reproduce the issue in latest M56 stable, but works fine in M57 Beta and M58 canary. Since M57 is going to be promoted in stable soon, don't think we need more debugging. Builds Tested ============= 56.0.2924.87 57.0.2987.88 58.0.3028.0 OS: Win10
,
Mar 7 2017
as per c#5 this issue not repro anymore on M57 and 58 |
||||
►
Sign in to add a comment |
||||
Comment 1 by woogie@chromium.org
, Mar 2 2017