Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.5.0
-
None
-
None
-
windows pro sp3 + tomcat 5.5 + JDK 1.5 + VC7
Description
We wrote a simple web service client program using AXIS2C-1.5 to access a java web service. In our test environment, there is about 2k memory leak in AXIS2C 1.5 web service client after each web service call. Then we traced down and found that the following statement in function "guththila_xml_reader_wrapper_xml_free" of the source file "\parser\guththila\guththila_xml_reader_wrapper.c" has been commented out.
if (data) AXIS2_FREE(env->allocator, data);
When we uncommented out this statment, Cmemleak program told us that the memory leak has been droped from 2k to 76 bytes. The report for the rest of memory leak is as follows:
FNH: files[i] deallocated ..\..\util\src\dir_handler.c: 316
FNH: files[i] deallocated ..\..\util\src\dir_handler.c: 316
FNH: files deallocated ..\..\util\src\dir_handler.c: 318
FNH: str_header deallocated ..\..\src\core\transport\http\sender\http_client.c: 282
FNH: output_stream deallocated ..\..\src\core\transport\http\sender\http_sender.c: 1339
Final Report
MLK: 00C81048 16 bytes allocated ..\..\util\src\error.c: 561
MLK: 00C81180 16 bytes allocated ..\..\util\src\string.c: 54
MLK: 00C811C8 24 bytes allocated ..\..\util\src\string.c: 81
MLK: 00CBDA58 20 bytes allocated ..\..\util\src\http_chunked_stream.c: 48
Total allocations : 4119
Max memory allocation: 1149486 (1122K)
Total leak : 76
could you please verify the modification? If you have special reason to comment out that statement, could you please let us know how to fix the major memory leak?