Menu

#3199 imm: memory leak in valgrind report

5.20.08
fixed
None
defect
unknown
d
minor
False
2020-07-13
2020-07-08
No
==368== 32,288 (224 direct, 32,064 indirect) bytes in 4 blocks are definitely lost in loss record 109 of 113
==368==    at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==368==    by 0x52AAB92: sysf_alloc_pkt (sysf_mem.c:429)
==368==    by 0x529A50D: ncs_enc_init_space (hj_ubaid.c:108)
==368==    by 0x1192FA: immd_process_immnd_down (immd_proc.c:801)
==368==    by 0x113302: immd_evt_proc_mds_evt (immd_evt.c:3274)
==368==    by 0x113302: immd_process_evt (immd_evt.c:127)
==368==    by 0x10B2C3: main (immd_main.c:390)

Related

Wiki: ChangeLog-5.20.08

Discussion

  • Chau Hoang Phuc

    Chau Hoang Phuc - 2020-07-10
    • status: assigned --> review
     
  • Chau Hoang Phuc

    Chau Hoang Phuc - 2020-07-13

    commit 693b8ad847a34e0f2ecfbf1390444d81892d87a3
    Author: phuc.h.chau phuc.h.chau@dektech.com.au
    Date: Thu Jul 9 10:30:31 2020 +0700

    imm: fix memory leak reported by valgrind [#3199]
    
    Fix definitely lost reported by valgrind.
    
     
  • Chau Hoang Phuc

    Chau Hoang Phuc - 2020-07-13
    • status: review --> fixed
     

Log in to post a comment.