Hi Ed,
[EMAIL PROTECTED] writes:
I have created some web service client code that uses the Axis2 library
functions and ran valgrind on my code to check for memory leak issues.
From what I have read, there should be no memory leaks from Axis2/C.
But, after running valgrind, the log indicated
Hi,
Please find my comments inline.
On 10/24/07, Stadelmann Josef [EMAIL PROTECTED] wrote:
Hi developer team,
I have ported almost a great part of AXIS2/C to HP Alpha/OpenVMS
so far, all basic libs (zlib, libxml2, ... ) a re running, are tested,
so far, libxml2 is built and test after
Hello David,
Were you able to run the test again after adding some of the free()
statements back in? Did it improve the performance? I am seeing a similar
issue where the memory footprint of the apache process keeps increasing
until a point when the server becomes very unresponsive and my client
Hi Dinesh,
I would be willing to help out in fixing the memory leak issues with
Axis2/C. I have used a couple tools to notice that the memory leaks
occur, but what would you recommend I should use to find out the exact
location of these memory leaks? How would I use valgrind to check for
the
Hi Ed,
I just had a brief look into the valgrind log you attached earlier, and
did a valgrind myself. There seem to be some issues in class_loader.c,
which I was checking today. Still couldn't locate the exact cause, :-).
But, I hope that a fix in that would resolve many issues.
Regards,
Senaka
Hi Ed,
[EMAIL PROTECTED] writes:
Hi Dinesh,
I would be willing to help out in fixing the memory leak issues with
Axis2/C.
That would be great !
I have used a couple tools to notice that the memory leaks
occur, but what would you recommend I should use to find out the exact
location of
I am running my tests with v1.1 but on Windows with apache 2.2.x (latest
September release). I tried various things. I did see one diff where the free
statement was either lost during the correction of an indentation or purposely
removed, however the free statement replacement did not solve the
