Opened 10 years ago
Closed 10 years ago
#4035 closed defect (fixed)
HEVC regression
Reported by: | cgbug | Owned by: | |
---|---|---|---|
Priority: | important | Component: | avcodec |
Version: | git-master | Keywords: | hevc regression |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | yes | |
Analyzed by developer: | no |
Description
Playback fails with git head. Worked ok with older build.
Regression was introduced between 20140811-git-5ec85c9 and 20140812-git-d6711ee.
Seems an infinite loop in nal parsing code?
Sample file:
https://www.sendspace.com/file/dn64ng
Output:
libavformat 56. 9.100 / 56. 9.100
libavdevice 56. 1.100 / 56. 1.100
libavfilter 5. 1.103 / 5. 1.103
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 1.100 / 53. 1.100
[hevc @ 02acdde0] Overread SPS by 8 bits
[hevc @ 02acdde0] SPS 0 does not exist.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
[hevc @ 02acdde0] Error parsing NAL unit #0.
[hevc @ 02acdde0] PPS id out of range: 0
<snip>
Change History (3)
comment:1 by , 10 years ago
Keywords: | hevc regression added |
---|---|
Priority: | normal → important |
Reproduced by developer: | set |
Status: | new → open |
comment:2 by , 10 years ago
Another sequence with invalid VUI, making uncertain what is parsed.
As there's nothing obvious as to why it overreads (the default window flag is set, and thus offsets are parsed, but there isn't enough data), and what the actual data there would be, I'm inclined to make that a "wontfix", all the more since there's no way to detect when that buggy header appears.
The file is not spec-compliant and another decoder could refuse it.
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | open → closed |
For future tickets: Please always provide your failing FFmpeg command line together with the complete, uncut console output.
Regressions since 5ec85c97