memory leak in omapip

[Randy Grimshaw]

Has anyone put a bug report in yet about the memory leak in omapip? It
appears to be unreleased allocations for ip.

[initially I traced the leak using valgrind:]
==9678==    at 0x3C01F38C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck.so)
==9678==    by 0x8050060: dmalloc (alloc.c:62)
==9678==    by 0x8050168: omapi_object_allocate (alloc.c:530)
==9678==    by 0x8053DA6: omapi_io_allocate (dispatch.c:40)
==9678==
==9678== LEAK SUMMARY:
==9678==    definitely lost: 5764 bytes in 131 blocks.
==9678==    possibly lost:   0 bytes in 0 blocks.
==9678==    still reachable: 183623 bytes in 4981 blocks.
==9678==         suppressed: 0 bytes in 0 blocks.
==9678== Reachable blocks (those to which a pointer was found) are not
shown.
==9678== To see them, rerun with: --show-reachable=yes
[which I should have done but didn't]

[then I bolted on Boehm garbage collector:]
Increasing heap size by 65536 after 0 allocated bytes
Initiating full world-stop collection 1 after 0 allocd bytes
--> Marking for collection 1 after 0 allocd bytes + 0 wasted bytes
Collection 0 finished ---> heapsize = 65536 bytes
World-stopped marking took 0 msecs
Complete collection took 0 msecs
syrdev:/usr/local/src/omcmd-0.4.3 # Increasing heap size by 65536 after
467648 allocated bytes
Initiating full world-stop collection 2 after 937880 allocd bytes
--> Marking for collection 2 after 937880 allocd bytes + 10464 wasted
bytes
Collection 1 finished ---> heapsize = 131072 bytes
World-stopped marking took 0 msecs
Complete collection took 0 msecs
Increasing heap size by 65536 after 146208 allocated bytes
Increasing heap size by 69632 after 805144 allocated bytes
Initiating full world-stop collection 3 after 1445344 allocd bytes
--> Marking for collection 3 after 1445344 allocd bytes + 18016 wasted
bytes
Collection 2 finished ---> heapsize = 266240 bytes
World-stopped marking took 10 msecs
Complete collection took 10 msecs
Increasing heap size by 90112 after 225992 allocated bytes
Increasing heap size by 122880 after 1150216 allocated bytes
Initiating full world-stop collection 4 after 2395080 allocd bytes
--> Marking for collection 4 after 2395080 allocd bytes + 24448 wasted
bytes
Collection 3 finished ---> heapsize = 479232 bytes
World-stopped marking took 10 msecs
Complete collection took 10 msecs
Increasing heap size by 163840 after 96096 allocated bytes
Increasing heap size by 217088 after 1821104 allocated bytes
Initiating full world-stop collection 5 after 4231248 allocd bytes
--> Marking for collection 5 after 4231248 allocd bytes + 44928 wasted
bytes
Collection 4 finished ---> heapsize = 860160 bytes
World-stopped marking took 10 msecs
Complete collection took 10 msecs
Increasing heap size by 290816 after 14440 allocated bytes
Increasing heap size by 385024 after 3305148 allocated bytes
Initiating full world-stop collection 6 after 7407104 allocd bytes
--> Marking for collection 6 after 7407104 allocd bytes + 105184 wasted
bytes
Collection 5 finished ---> heapsize = 1536000 bytes
World-stopped marking took 20 msecs
Complete collection took 20 msecs
Increasing heap size by 516096 after 118404 allocated bytes
Increasing heap size by 688128 after 3412736 allocated bytes
Initiating full world-stop collection 7 after 4620768 allocd bytes
--> Marking for collection 7 after 4620768 allocd bytes + 106240 wasted
bytes
Collection 6 finished ---> heapsize = 2740224 bytes
World-stopped marking took 30 msecs
Complete collection took 30 msecs
Increasing heap size by 917504 after 29832 allocated bytes
[which leads me to believe this is not a garbage collection problem]

Thank you in advance.
<><Randy


<><Randall Grimshaw
Room 203 Machinery Hall
Syracuse University
Syracuse, NY   13244
315-443-5779
rgrimsha at syr.edu