[ http://issues.apache.org/jira/browse/AXISCPP-674?page=comments#action_12320662 ]
Henrik Nordberg commented on AXISCPP-674: ----------------------------------------- Jonathan, what are you suggesting? operator delete is allowed to change the pointer after deleting it. Thus this is unsafe: int *p = 0; delete p; // safe delete p; // an error, because p may not be 0 any longer If what you are saying is just adjusting memory so that delete will act on the same location the next time, then that may hide the problem, but it will not get rid of it. > Memory leak > ----------- > > Key: AXISCPP-674 > URL: http://issues.apache.org/jira/browse/AXISCPP-674 > Project: Axis-C++ > Type: Bug > Versions: 1.5 Final > Environment: Win2000 > Reporter: Mark Kolb > Assignee: Samisa Abeysinghe > Priority: Critical > > When running a simple client test in a loop both the client and server memory > continue to climb and never come back down. I used the calculator example > and modified it with a loop around the add. I noticed the memory climbing > very quickly in the client using performance viewer for that process. Also, > the server process which is listed as Apache#1 also has a memory leak. It is > using the Calculator.dll that is part of the Axis package. This occurred > for both HTTP and HTTPS protocols. I did this test with the 1.5 Final > release. -- 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
