Axis2-C
  1. Axis2-C
  2. AXIS2C-695

memory leak fixes in directory handler

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.1.0
    • Component/s: util
    • Labels:
      None
    • Environment:
      windows

      Description

      for windows version, clearing the files is commented by ifndef win32. Because of that, memory leak occurs.
      Also, when closing the directory, even if the return value is -1, still the memory has to be cleared.

        Activity

        Hide
        S.Uthaiyashankar added a comment -

        patch to remove the memory leak

        Show
        S.Uthaiyashankar added a comment - patch to remove the memory leak
        Hide
        Samisa Abeysinghe added a comment -

        The patch has been applied. Thaks for the patch

        Show
        Samisa Abeysinghe added a comment - The patch has been applied. Thaks for the patch
        Hide
        David Klassen added a comment -

        This week using v1.0 I saw some amazing memory leaks using the apache module on Windows (Logging set to debug.), and a simple shell script from a Linux client . The httpd.exe resident program memory size was about 25M at start-up. Simulating 60 concurrent users making one request per second, using the 'echo' sample program. The process memory size jumped to 300M over the period of the tests. So far I have not tried to find where the memory leak is (But it seems S.Uthaiyashankar has), however I am very excited to try v1.1 and make another assessment now that I see a similar issue has already been looked into. I will provide an update with any information and conclusions I discover. Thanks, for the new release.

        Show
        David Klassen added a comment - This week using v1.0 I saw some amazing memory leaks using the apache module on Windows (Logging set to debug.), and a simple shell script from a Linux client . The httpd.exe resident program memory size was about 25M at start-up. Simulating 60 concurrent users making one request per second, using the 'echo' sample program. The process memory size jumped to 300M over the period of the tests. So far I have not tried to find where the memory leak is (But it seems S.Uthaiyashankar has), however I am very excited to try v1.1 and make another assessment now that I see a similar issue has already been looked into. I will provide an update with any information and conclusions I discover. Thanks, for the new release.

          People

          • Assignee:
            Malinda Kaushalye Kapuruge
            Reporter:
            S.Uthaiyashankar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development