[ 
https://issues.apache.org/jira/browse/AXIS2C-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613039#action_12613039
 ] 

Damitha Kumarage commented on AXIS2C-1156:
------------------------------------------

Hi Diluka,
Applied your patch.
But still valgrind show a context error an leaks in client side. It is good to 
know whether this context error is caused by Savan/C.

==32284== Invalid free() / delete / delete[]
==32284==    at 0x4022B8A: free (vg_replace_malloc.c:323)
==32284==    by 0x4296C4B: (within /lib/i686/cmov/libc-2.7.so)
==32284==    by 0x4296773: __libc_freeres (in /lib/i686/cmov/libc-2.7.so)
==32284==    by 0x401E216: _vgnU_freeres (vg_preloaded.c:60)
==32284==    by 0x4214EC3: _Exit (in /lib/i686/cmov/libc-2.7.so)
==32284==    by 0x4195457: (below main) (in /lib/i686/cmov/libc-2.7.so)
==32284==  Address 0x417a580 is not stack'd, malloc'd or (recently) free'd
==32284==
==32284== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 75 from 2)
==32284== malloc/free: in use at exit: 1,436 bytes in 17 blocks.
==32284== malloc/free: 17,255 allocs, 17,239 frees, 870,840 bytes allocated.
==32284== For counts of detected errors, rerun with: -v
==32284== searching for pointers to 17 not-freed blocks.
==32284== checked 204,184 bytes.
==32284==
==32284==
==32284== 864 (48 direct, 816 indirect) bytes in 2 blocks are definitely lost 
in loss record 6 of 6
==32284==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==32284==    by 0x4030A8C: axutil_allocator_malloc_impl (in 
/axis2c/deploy/lib/libaxutil.so.0.5.0)
==32284==    by 0x40308FB: axutil_hash_make (in 
/axis2c/deploy/lib/libaxutil.so.0.5.0)
==32284==    by 0x80491BD: main (subscriber.c:89)
==32284==
==32284== LEAK SUMMARY:
==32284==    definitely lost: 48 bytes in 2 blocks.
==32284==    indirectly lost: 816 bytes in 11 blocks.
==32284==      possibly lost: 0 bytes in 0 blocks.
==32284==    still reachable: 572 bytes in 4 blocks.



Also in the server side there are leaks.

==32379== 136 bytes in 1 blocks are possibly lost in loss record 4 of 12
==32379==    at 0x4021E22: calloc (vg_replace_malloc.c:397)
==32379==    by 0x4010627: (within /lib/ld-2.7.so)
==32379==    by 0x40106EB: _dl_allocate_tls (in /lib/ld-2.7.so)
==32379==    by 0x4152C3C: pthread_create@@GLIBC_2.1 (in 
/lib/i686/cmov/libpthread-2.7.so)
==32379==    by 0x407DBF6: axutil_thread_create (in 
/axis2c/deploy/lib/libaxutil.so.0.5.0)
==32379==    by 0x40747C4: axutil_thread_pool_get_thread (in 
/axis2c/deploy/lib/libaxutil.so.0.5.0)
==32379==    by 0x4734114: ???
==32379==    by 0x40E0DF8: (within /axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x40E1235: axis2_build_conf_ctx (in 
/axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x411FE3A: axis2_http_server_create (in 
/axis2c/deploy/lib/libaxis2_http_receiver.so.0.5.0)
==32379==    by 0x8057A47: (within /axis2c/deploy/bin/axis2_http_server)
==32379==    by 0x419544F: (below main) (in /lib/i686/cmov/libc-2.7.so)
==32379==
==32379==
==32379== 440 bytes in 10 blocks are definitely lost in loss record 7 of 12
==32379==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==32379==    by 0x46E4483: ???
==32379==    by 0x4701A85: ???
==32379==    by 0x4723E56: ???
==32379==    by 0x46DB01A: ???
==32379==    by 0x46D74C7: ???
==32379==    by 0x46D7B4E: ???
==32379==    by 0x46D7B4E: ???
==32379==    by 0x40BAF3C: axis2_handler_invoke (in 
/axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x40C0C22: axis2_phase_invoke (in 
/axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x40C440D: axis2_engine_invoke_phases (in 
/axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x40C4F71: axis2_engine_receive (in 
/axis2c/deploy/lib/libaxis2_engine.so.0.5.0)
==32379==    by 0x409AEFA: axis2_http_transport_utils_process_http_post_request 
(in /axis2c/deploy/lib/libaxis2_http_common.so.0.5.0)
==32379==
==32379==
==32379== 528 bytes in 12 blocks are definitely lost in loss record 8 of 12
==32379==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==32379==    by 0x4897B63: ???
==32379==    by 0x48B5165: ???
==32379==    by 0x48D7F50: ???
==32379==    by 0x488C0F4: ???
==32379==    by 0x473403D: ???
==32379==    by 0x407D7E5: (within /axis2c/deploy/lib/libaxutil.so.0.5.0)
==32379==    by 0x41524FA: start_thread (in /lib/i686/cmov/libpthread-2.7.so)
==32379==    by 0x4255D7D: clone (in /lib/i686/cmov/libc-2.7.so)
==32379==
==32379==
==32379== 9,725 (1,866 direct, 7,859 indirect) bytes in 35 blocks are 
definitely lost in loss record 12 of 12
==32379==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==32379==    by 0x406BA8C: axutil_allocator_malloc_impl (in 
/axis2c/deploy/lib/libaxutil.so.0.5.0)
==32379==    by 0x40334A8: axiom_node_create (in 
/axis2c/deploy/lib/libaxis2_axiom.so.0.5.0)
==32379==    by 0x4038B44: axiom_element_create (in 
/axis2c/deploy/lib/libaxis2_axiom.so.0.5.0)
==32379==    by 0x4733F47: ???
==32379==    by 0x407D7E5: (within /axis2c/deploy/lib/libaxutil.so.0.5.0)
==32379==    by 0x41524FA: start_thread (in /lib/i686/cmov/libpthread-2.7.so)
==32379==    by 0x4255D7D: clone (in /lib/i686/cmov/libc-2.7.so)
==32379==
==32379== LEAK SUMMARY:
==32379==    definitely lost: 2,834 bytes in 57 blocks.
==32379==    indirectly lost: 7,859 bytes in 274 blocks.
==32379==      possibly lost: 136 bytes in 1 blocks.
==32379==    still reachable: 2,282 bytes in 57 blocks.


> memory leak in savanc
> ---------------------
>
>                 Key: AXIS2C-1156
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1156
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>         Environment: linux fc5
>            Reporter: Frederic Heem
>            Assignee: Damitha Kumarage
>             Fix For: 1.4.1
>
>         Attachments: in_handler.patch, sub_processor.patch
>
>
> In savan_in_handler_invoke(), a processor is created by 
> savan_sub_processor_create()  but it is not freed, actually, there isn't a 
> function to free it (savan_sub_processor_free() ?)
> Also there is a mix of tab and spaces in the file which makes it difficult to 
> read and maintain.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to