Releases: ittiam-systems/libavc
Releases · ittiam-systems/libavc
v1.6.0
What's Changed
- libavc : Fix mutex initialization index in apv_proc_start_mutex by @suyogpawar20 in #105
- libavc : Enable support for MacOS by @suyogpawar20 in #106
- libavc: Add VSCode configuration files for Linux & MacOS by @sushant191k in #107
- libavcdec: Fix integer overflow issue in ui_max_frame_num by @rakeshnitb in #108
New Contributors
- @sushant191k made their first contribution in #107
- @rakeshnitb made their first contribution in #108
Full Changelog: v1.5.0...v1.6.0
v1.5.0
What's Changed
- mvcdec: Heap overflow in 'ih264d_read_coeff4x4_cabac' by @AshwinNatesan-ittiam in #98
- oss-fuzz heap buffer overflow and timeout by @MallikarjunKamble in #101
- svcdec: Handled timeout by returning status of the error by @MallikarjunKamble in #102
- Limit decode calls to a maximum of 100 to prevent potential timeouts with fuzzers by @MallikarjunKamble in #103
- libavc: Fix poc counts for idr slice by @suyogpawar20 in #104
New Contributors
- @suyogpawar20 made their first contribution in #104
Full Changelog: v1.4.0...v1.5.0
v1.4.0
v1.3.0
libavcenc: use number_t while computing number of bits in period For large intra frame intervals or for a choice of bit rate that causes large bits per frame, it possible that while computing number of bits available in the gop overflow the datatype bounds. For these calculations use number_t as this offers wider space Bug: oss-fuzz-63044 Test: avc_enc_fuzzer Change-Id: Ifee9130f0021f77905aea67832abc044537088e5