Standards Based Linux Instrumentation / Bugs / #2220 Memory leak in method invoke using SFCB local interface

#2220 Memory leak in method invoke using SFCB local interface

Milestone: Memory_Leak

Status: pending-fixed

Owner: Chris Buccella

Labels: sfcb (1090)

Component:

Priority: 5

Updated: 2011-06-10

Created: 2011-06-10

Creator: Chris Poblete

Private: No

Memory leak is detected for each method invoke when using the SFCB local interface. Valgrind and code review shows the leak in the function invokeMethod when heap allocated class clone is not freed.

252,320 bytes in 5 blocks are definitely lost in loss record 57 of 57
at 0x40053C0: malloc (vg_replace_malloc.c:149)
by 0x558C01E: cls_clone (constClass.c:430)
by 0x5565F45: getClass (cimcClientSfcbLocal.c:1608)
by 0x55656A0: invokeMethod (cimcClientSfcbLocal.c:1447)
by 0x4156236: cim_invoke_method (sfcc-interface.c:2025)
...

The leak is significant on embedded environment. The proposed fix is attached for your review.

Discussion

Chris Poblete - 2011-06-10

proposed fix

patch-sfcb-1.3.10-invokemethod-memleak-fix.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2011-06-10

labels: 736624 --> sfcb

status: open --> open-accepted
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2011-06-10

status: open-accepted --> pending-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2011-06-10

committed to CVS HEAD and git master

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Memory leak in method invoke using SFCB local interface

Group

Searches

Help

#2220 Memory leak in method invoke using SFCB local interface

Discussion