Custom Query (1442 matches)
Results (7 - 9 of 1442)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#57 | duplicate | Excessive memory allocation | fbossen | |
Description |
Memory allocation is excessive, possibly leading to crashes. Memory usage has been analyzed for the following case: class B encoding with max CU=32x32, memory snapshot during encoding of 2nd frame
9 TComList objects 2040 CUs per frame 3 32x32 integer arrays per CU (luma+2*chroma), each array is 4KB 9 * 2040 * 3 * 32 * 32 * 4 = 215MB
Also see attached jpeg file |
|||
#59 | fixed | Memory issue - unnecessarily long variable type | wjhan | |
Description |
Comments from Tourapis, Alexis. Thanks! Currently motion vector and reference indices use Int-type variable. There are other cases using unnecessarily long variable type. Check them and replace them by suitable types. It can reduce memory considerably. |
|||
#60 | fixed | Configurability of chroma interpolation filter | wjhan | |
Description |
Current software uses bi-linear interpolation filter for chroma when InterpFilterType=0, 3 and 4 while luma 1/8th filter is used for InterpFilterType=1 and 2. Configurability of the use of luma 1/8th interpolation filter for chroma (possibly different default number of taps of chroma, but not new filter) is preferable. |