axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2C-399) memory leaks
Date Mon, 13 Nov 2006 00:19:37 GMT
    [ http://issues.apache.org/jira/browse/AXIS2C-399?page=comments#action_12449213 ] 
            
Samisa Abeysinghe commented on AXIS2C-399:
------------------------------------------

If you run valgrind with '--leak-check=full' it would reveal the exact leak locations.
I am working currently to fix the leaks on client side. Next is to look at server side.


> memory leaks
> ------------
>
>                 Key: AXIS2C-399
>                 URL: http://issues.apache.org/jira/browse/AXIS2C-399
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: linux simple http server
>            Reporter: Marc Giger
>
> I see massive memory leaks with the Simple Axis2 HTTP Server.
> Because I can't test it with mod_axis2 I can only report it with the simple http server.
> Here are two valgrind outputs:
> The first one is with a shoot to the sample echo service:
> Started Simple Axis2 HTTP Server ...
> ==19904==
> ==19904== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 45 from
> 1) ==19904== malloc/free: in use at exit: 71,000 bytes in 1,038 blocks.
> ==19904== malloc/free: 15,119 allocs, 14,081 frees, 1,513,871 bytes
> allocated. ==19904== For counts of detected errors, rerun with: -v
> ==19904== searching for pointers to 1,038 not-freed blocks.
> ==19904== checked 8,697,064 bytes.
> ==19904==
> ==19904== LEAK SUMMARY:
> ==19904==    definitely lost: 70,309 bytes in 1,023 blocks.
> ==19904==      possibly lost: 136 bytes in 1 blocks.
> ==19904==    still reachable: 555 bytes in 14 blocks.
> ==19904==         suppressed: 0 bytes in 0 blocks.
> ==19904== Use --leak-check=full to see details of leaked memory.
> This second one is with a service built with the skeleton generator and
> no data binding but just XML in/out:
> Started Simple Axis2 HTTP Server ...
> ==13034==
> ==13034== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 46 from
> 1) ==13034== malloc/free: in use at exit: 200,214 bytes in 1,025 blocks.
> ==13034== malloc/free: 24,826 allocs, 23,801 frees, 2,676,022 bytes
> allocated. ==13034== For counts of detected errors, rerun with: -v
> ==13034== searching for pointers to 1,025 not-freed blocks.
> ==13034== checked 8,697,064 bytes.
> ==13034==
> ==13034== LEAK SUMMARY:
> ==13034==    definitely lost: 199,523 bytes in 1,010 blocks.
> ==13034==      possibly lost: 136 bytes in 1 blocks.
> ==13034==    still reachable: 555 bytes in 14 blocks.
> ==13034==         suppressed: 0 bytes in 0 blocks.
> ==13034== Use --leak-check=full to see details of leaked memory.
> My service function looks like the following:
> axiom_node_t* axis2_skel_TestService_Test (const axis2_env_t *env,
> 					      axiom_node_t* param0 )
> {
> 	return param0;
> }
> In this case i sent a document with about 34KB in size.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message