When WebPSafeMalloc fails on VP8LHuffmanTablesAllocate,
next is not initialized to NULL.
VP8LHuffmanTablesDeallocate uses next to know the following nodes.
A patch fixes this issue.
Change-Id: I144ae84cd97e5bca227018ef1afa95361267902c
The first condition is only necessary if we have not read enough
(enough being defined by src_last, not src_end which is the end
of the image).
The second condition now fits the comment below: "if not
incremental, and we are past the end of buffer".
BUG=oss-fuzz:62136
Change-Id: I0700f67c62db8e1c02c2e429a069a71e606a5e4f
First, BuildHuffmanTable is called to check if the data is valid.
If it is and the table is not big enough, more memory is allocated.
This will make sure that valid (but unoptimized because of unbalanced
codes) streams are still decodable.
Bug: chromium:1479274
Change-Id: I31c36dbf3aa78d35ecf38706b50464fd3d375741
- #501: basic support (doesn't work yet, doesn't crash) from M1294490 (630d19190)
- #501: add toggle pref (ac0300a55)
- #501: functional decoder wrapper (339688135)
- #501: libwebp 1.0.1 with endian fix to highlevel decoder (c2ce1fbd0)
- #501: convert to Demux API; add colour profile support (ceed59655)
- #501: make animated WebP failures fatal for now (ed1453647)
- #516: try to be aggressive again with global window idle timeout (f281a6bf8)
- Bug 1270591. Add support for checking for AVX & AVX2. Detecting AVX2 requires the use of a sub-leaf. (789319bd0)
- update libwebp to 0.6.1 (afa956138)
- fix build on intel for libwebp 0.6 (97193d7a0)
Vincent Rabaud
Masahiro Hanada
roytam1