Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#750 RxApi memory never released on RexxStart

v4.0
closed
Rick McGuire
APIs (66)
5
2012-08-14
2009-07-08
Laurent Crepel
No

We are testing Rexx ooRexx-4.0.0-4881 RC.
Test is done on Windows XP SP4.

When RexxStart is called via a C++ program the RxAPi memory increases
and when this program is sleeping the memory is never free.

Not the same issue as the bug 2817468.
Step to reproduce (See attached sample)
Set Hello.rex in C:\
Start the CvHello.exe
Check RxApi memory. The memory increases.
Look the memory usage in task manager
RxApi memory never released whereas program calls a Sleep() frequently

Discussion

  • Mark Miesfeld
    Mark Miesfeld
    2009-07-08

    Laurent,

    1.) The zip file you attached seems to be bad. I tried downloading it several times and allways get:

    C:>unzip Hello2.zip
    Archive: Hello2.zip
    warning [Hello2.zip]: 71 extra bytes at beginning or within zipfile
    (attempting to process anyway)
    file #1: bad zipfile offset (local header sig): 71
    (attempting to re-compensate)
    file #1: bad zipfile offset (local header sig): 71
    file #2: bad zipfile offset (local header sig): 101

    2.) I'm not sure why you think this is a bug.

    Could you try putting up another zip file. Thanks.

     
  • Rick McGuire
    Rick McGuire
    2009-07-08

    Mark, I was able to recreate this and locate the source of the leak. Working on the appropriate fix now.

     
  • Rick McGuire
    Rick McGuire
    2009-07-08

    Committed revision 4888.

    The memory leak was in the internal API used to resolve the entry point address of the registered exits, which is why this only showed up with your application and not programs launched from the command line.

     


Anonymous


Cancel   Add attachments