RE: Memory leak report for Axis2c 1.4
Is it safe to uncomment AXIS2_FREE call to avoid memory leaks?
This leak still exists in 1.5 also.
From: Milinda Pathirage [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 15, 2008 10:01 PM
To: Apache AXIS C User List
Subject: Re: Memory leak report for Axis2c 1.4
Hi all,
I think this leak only exists in Windows. This is caused by following
code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above
kind of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in
Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED]
wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c:
guththila_xml_reader_wrapper_xml_free(), line 581, call to AXIS2_FREE()
for string buffer was commented, cause tens K memory leak for each
request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694.
When nmsp_found is FALSE, namesp pointer will be pushed into stack,
however when it's FALSE, namesp pointer will not be used and not be
freed.
I thought we fixed all the leaks before the release. What is the code
you are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
---
Confidentiality Notice: This electronic mail transmission is confidential,
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system.
Re: Memory leak report for Axis2c 1.4
Hatim Daginawala wrote:
Is it safe to uncomment AXIS2_FREE call to avoid memory leaks?
You can try :)
Samisa...
This leak still exists in 1.5 also.
*From:* Milinda Pathirage [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 15, 2008 10:01 PM
*To:* Apache AXIS C User List
*Subject:* Re: Memory leak report for Axis2c 1.4
Hi all,
I think this leak only exists in Windows. This is caused by following
code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above
kind of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c:
guththila_xml_reader_wrapper_xml_free(), line 581, call to
AXIS2_FREE() for string buffer was commented, cause tens K memory leak
for each request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694.
When nmsp_found is FALSE, namesp pointer will be pushed into stack,
however when it's FALSE, namesp pointer will not be used and not be freed.
I thought we fixed all the leaks before the release. What is the code
you are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
---
Confidentiality Notice: This electronic mail transmission is
confidential,
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system.
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.5.7/1581 - Release Date: 7/30/2008 6:56 AM
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak report for Axis2c 1.4
I have tried and it seems to be working for my test program. However, I
would like to understand why the code was commented out. That may help
me evaluate the risk.
Thanks
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 4:12 PM
To: Apache AXIS C User List
Subject: Re: Memory leak report for Axis2c 1.4
Hatim Daginawala wrote:
Is it safe to uncomment AXIS2_FREE call to avoid memory leaks?
You can try :)
Samisa...
This leak still exists in 1.5 also.
*From:* Milinda Pathirage [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 15, 2008 10:01 PM
*To:* Apache AXIS C User List
*Subject:* Re: Memory leak report for Axis2c 1.4
Hi all,
I think this leak only exists in Windows. This is caused by following
code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above
kind of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in
Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c:
guththila_xml_reader_wrapper_xml_free(), line 581, call to
AXIS2_FREE() for string buffer was commented, cause tens K memory leak
for each request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694.
When nmsp_found is FALSE, namesp pointer will be pushed into stack,
however when it's FALSE, namesp pointer will not be used and not be
freed.
I thought we fixed all the leaks before the release. What is the code
you are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
---
Confidentiality Notice: This electronic mail transmission is
confidential,
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system.
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.5.7/1581 - Release Date:
7/30/2008 6:56 AM
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Confidentiality Notice: This electronic mail transmission is confidential,
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak report for Axis2c 1.4
You could have a look at the rationale by looking at the svn log for
that change.
http://svn.apache.org/viewvc/webservices/axis2/trunk/c/
Thanks,
Samisa...
Hatim Daginawala wrote:
I have tried and it seems to be working for my test program. However, I
would like to understand why the code was commented out. That may help
me evaluate the risk.
Thanks
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 4:12 PM
To: Apache AXIS C User List
Subject: Re: Memory leak report for Axis2c 1.4
Hatim Daginawala wrote:
Is it safe to uncomment AXIS2_FREE call to avoid memory leaks?
You can try :)
Samisa...
This leak still exists in 1.5 also.
*From:* Milinda Pathirage [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 15, 2008 10:01 PM
*To:* Apache AXIS C User List
*Subject:* Re: Memory leak report for Axis2c 1.4
Hi all,
I think this leak only exists in Windows. This is caused by following
code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above
kind of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in
Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c:
guththila_xml_reader_wrapper_xml_free(), line 581, call to
AXIS2_FREE() for string buffer was commented, cause tens K memory leak
for each request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694.
When nmsp_found is FALSE, namesp pointer will be pushed into stack,
however when it's FALSE, namesp pointer will not be used and not be
freed.
I thought we fixed all the leaks before the release. What is the code
you are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
---
Confidentiality Notice: This electronic mail transmission is
confidential,
may be privileged and should be read or retained only by the intended
recipient. If you have received this transmission in error, please
immediately notify the sender and delete it from your system.
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.5.7/1581 - Release Date:
7/30/2008 6:56 AM
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak report for Axis2c 1.4
Hi Steven,
The second issue that you mentioned is a memory leak and I have created a
Jira and fixed the issue in the trunk. Please check weather my fix solved
the problem.
http://issues.apache.org/jira/browse/AXIS2C-1144
Regards,
Supun..
On Fri, May 16, 2008 at 8:30 AM, Milinda Pathirage
[EMAIL PROTECTED] wrote:
Hi all,
I think this leak only exists in Windows. This is caused by following code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above kind
of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED]
wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(),
line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K
memory leak for each request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When
nmsp_found is FALSE, namesp pointer will be pushed into stack, however when
it's FALSE, namesp pointer will not be used and not be freed.
I thought we fixed all the leaks before the release. What is the code you
are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
Re: Memory leak report for Axis2c 1.4
Steven Zhang wrote: Hi: I just finded memory leak in Axis2 1.4 GUTHTHILA: 1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(), line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K memory leak for each request. Why this one is commented? 2. guththila_xml_writer.c: guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When nmsp_found is FALSE, namesp pointer will be pushed into stack, however when it's FALSE, namesp pointer will not be used and not be freed. I thought we fixed all the leaks before the release. What is the code you are using to test for leaks? Did you try with echo sample? Samisa... Am I correct? Thanks. Steven Zhang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 - Release Date: 5/15/2008 7:24 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak report for Axis2c 1.4 - one more
One more memory leak: src\core\transport\http\sender\http_client.c: axis2_http_client_recieve_header(), line 486, status_line pointer. There is a while loop to receive and parse multiple status lines from HTTP header into status_line pointer, howerver this pointer is freed for only once at line 552. I downloaded release 1.4 at May 9th, I think it should be the formal version. Steven Zhang - Original Message - From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Thursday, May 15, 2008 3:34 PM Subject: Re: Memory leak report for Axis2c 1.4 Steven Zhang wrote: Hi: I just finded memory leak in Axis2 1.4 GUTHTHILA: 1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(), line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K memory leak for each request. Why this one is commented? 2. guththila_xml_writer.c: guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When nmsp_found is FALSE, namesp pointer will be pushed into stack, however when it's FALSE, namesp pointer will not be used and not be freed. I thought we fixed all the leaks before the release. What is the code you are using to test for leaks? Did you try with echo sample? Samisa... Am I correct? Thanks. Steven Zhang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 - Release Date: 5/15/2008 7:24 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak report for Axis2c 1.4 - one more
Steven Zhang wrote: One more memory leak: src\core\transport\http\sender\http_client.c: axis2_http_client_recieve_header(), line 486, status_line pointer. There is a while loop to receive and parse multiple status lines from HTTP header into status_line pointer, howerver this pointer is freed for only once at line 552. I downloaded release 1.4 at May 9th, I think it should be the formal version. Yes that is the correct one. Again what is the client code you are using? Samisa... Steven Zhang - Original Message - From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Thursday, May 15, 2008 3:34 PM Subject: Re: Memory leak report for Axis2c 1.4 Steven Zhang wrote: Hi: I just finded memory leak in Axis2 1.4 GUTHTHILA: 1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(), line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K memory leak for each request. Why this one is commented? 2. guththila_xml_writer.c: guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When nmsp_found is FALSE, namesp pointer will be pushed into stack, however when it's FALSE, namesp pointer will not be used and not be freed. I thought we fixed all the leaks before the release. What is the code you are using to test for leaks? Did you try with echo sample? Samisa... Am I correct? Thanks. Steven Zhang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 - Release Date: 5/15/2008 7:24 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 - Release Date: 5/15/2008 7:24 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak report for Axis2c 1.4
Hi all,
I think this leak only exists in Windows. This is caused by following code.
#ifdef WIN32
attr_name_str = axutil_string_create(env, attr_name);
axiom_xml_reader_xml_free(om_builder-parser, env, attr_name);
#else
There are so many places in om_stax_builder.c where we have used above kind
of logic. Because we have comment out the reported code block:
void AXIS2_CALL
guththila_xml_reader_wrapper_xml_free(
axiom_xml_reader_t * parser,
const axutil_env_t * env,
void *data)
{
/*if (data)
AXIS2_FREE(env-allocator, data); */
}
in guththila wrapper, it caused memory leaks in windows but not in Linux.
Thanks
Milinda.
On Fri, May 16, 2008 at 4:04 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Steven Zhang wrote:
Hi:
I just finded memory leak in Axis2 1.4 GUTHTHILA:
1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(),
line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K
memory leak for each request. Why this one is commented?
2. guththila_xml_writer.c:
guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When
nmsp_found is FALSE, namesp pointer will be pushed into stack, however when
it's FALSE, namesp pointer will not be used and not be freed.
I thought we fixed all the leaks before the release. What is the code you
are using to test for leaks? Did you try with echo sample?
Samisa...
Am I correct?
Thanks.
Steven Zhang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 -
Release Date: 5/15/2008 7:24 AM
--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - The Open Source SOA Company
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://inf-dimensions.blogspot.com Infinite Dimensions
http://wsaxc.blogspot.com Web Services With Axis2/C
Re: Memory leak report for Axis2c 1.4 - one more
Hi Steven, Could you please create a Jira for this issue. That would be easy to manage. thanks, Dinesh On Fri, May 16, 2008 at 5:05 AM, Steven Zhang [EMAIL PROTECTED] wrote: One more memory leak: src\core\transport\http\sender\http_client.c: axis2_http_client_recieve_header(), line 486, status_line pointer. There is a while loop to receive and parse multiple status lines from HTTP header into status_line pointer, howerver this pointer is freed for only once at line 552. I downloaded release 1.4 at May 9th, I think it should be the formal version. Steven Zhang - Original Message - From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Thursday, May 15, 2008 3:34 PM Subject: Re: Memory leak report for Axis2c 1.4 Steven Zhang wrote: Hi: I just finded memory leak in Axis2 1.4 GUTHTHILA: 1. guththila_xml_read_wrapper.c: guththila_xml_reader_wrapper_xml_free(), line 581, call to AXIS2_FREE() for string buffer was commented, cause tens K memory leak for each request. Why this one is commented? 2. guththila_xml_writer.c: guththila_write_empty_element_with_prefix_and_namespace(), line 1694. When nmsp_found is FALSE, namesp pointer will be pushed into stack, however when it's FALSE, namesp pointer will not be used and not be freed. I thought we fixed all the leaks before the release. What is the code you are using to test for leaks? Did you try with echo sample? Samisa... Am I correct? Thanks. Steven Zhang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1434 - Release Date: 5/15/2008 7:24 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://nethu.org/
