#1080 RXAPI memory not released at end

vX.X.X
pending
Rick McGuire
APIs (66)
5
2012-08-14
2012-06-16
John Timmons
No

Version: ooRexx 4.1.1 (MT) 6.03 Rel 16-May-2012
Operating System: Windows 7, up-to-date
Test Program: THE 3.3RC1 Rel 10-July-2011
Cross-Reference: THE 3.3RC1 Bug Report 3535446

Discussion

  • John Timmons
    John Timmons
    2012-06-16

    See Details above.
    Also see Attached File containing data points concerning RXAPI sizes.

     
  • Rick McGuire
    Rick McGuire
    2012-06-16

    You are going to need to be more specific as why you feel the memory is not being released and provide some steps for recreating this.

     
  • John Timmons
    John Timmons
    2012-06-18

    bigrixx,
    I have attached a file of data points taken from Resource Monitor I recorded by hand during an observation of multiple THE edit sessions. They seem to indicate that the Commit, Working Set, and Private memory allocations of RXAPI keep going up incrementally. The Shared memory seems to stay about the same. If this is normal for whatever reason, please let me know and we can forget the whole thing. In the meantime, I am pursuing how to get logged data out of Performance Monitor. Microsoft does not make it easy (by design, I'm sure), but the implications are that one can trap logged performance data. And I don't know at this point how to trap a dump out of RXAPI that would have any meaning to you, i.e., during or right after the crash. Again Microsoft is no help. If you know how, please let me know.

    johnbsayles

     
  • Rick McGuire
    Rick McGuire
    2012-06-29

    I've been able to recreate this memory leak using some of our API unit test programs, so taking THE out of the equation will make this simpler. The fix may be somewhat complicated and will likely require an extensive testing period, so I can't project how soon one might be available.

     


Anonymous


Cancel   Add attachments