Opened 4 years ago

Closed 3 years ago

#1370 closed defect (fixed)

Memory leak in `EncCu::xCheckRDCostMergeGeo2Nx2N`

Reported by: dumas Owned by:
Priority: major Milestone: VTM-11.2
Component: VTM Version: VTM-10.0rc1
Keywords: Memory leak Cc: ksuehring, XiangLi, fbossen, jvet@…

Description

Using VTM-10 compiled with Address Sanitizer, when encoding a video sequence in random-access, memory leaks appear in EncCu::xCheckRDCostMergeGeo2Nx2N. The same problem occurs when using either VTM-9 or VTM-8 instead of VTM-10.
For instance, when encoding "D_BasketballPass" in 4:2:0 via VTM-8.0 compiled with Address Sanitizer and using the standard configuration file for random-access, the beginning of the log reporting the memory leaks is given in the attachment "sanitizer_memory_leak_xCheckRDCostMergeGeo2Nx2N.png".
This arises from the fact that, in EncCu::xCheckRDCostMergeGeo2Nx2N, the dynamically allocated memories for the pointers sadWholeBlk, pocMrg, MrgMv, and isSkipThisCand are not freed before returning from either here https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/blob/45dfe06835aea43f37456ea54972ef31b765eacf/source/Lib/EncoderLib/EncCu.cpp#L2899 or from here https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/blob/45dfe06835aea43f37456ea54972ef31b765eacf/source/Lib/EncoderLib/EncCu.cpp#L2922.

Attachments (1)

sanitizer_memory_leak_xCheckRDCostMergeGeo2Nx2N.PNG (13.6 KB) - added by dumas 4 years ago.
View of the beginning of the log reporting the memory leaks.

Download all attachments as: .zip

Change history (2)

Changed 4 years ago by dumas

View of the beginning of the log reporting the memory leaks.

comment:1 Changed 3 years ago by fbossen

  • Milestone set to VTM-11.2
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.