Menu
▾
▴
[Oorexx-bugs] [ oorexx-Bugs-3535652 ] RXAPI memory not released at end
|
From: SourceForge.net <no...@so...> - 2012-08-07 13:48:48
|
Bugs item #3535652, was opened at 2012-06-16 04:58 Message generated for change (Settings changed) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3535652&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: APIs >Group: vX.X.X Status: Pending Resolution: Fixed Priority: 5 Private: No Submitted By: John Timmons (johnbsayles) Assigned to: Rick McGuire (bigrixx) Summary: RXAPI memory not released at end Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2012-06-29 10:41 Message: Committed revision 7975. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2012-06-29 07:53 Message: 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. ---------------------------------------------------------------------- Comment By: John Timmons (johnbsayles) Date: 2012-06-18 15:55 Message: 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 ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2012-06-16 05:07 Message: 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. ---------------------------------------------------------------------- Comment By: John Timmons (johnbsayles) Date: 2012-06-16 05:05 Message: See Details above. Also see Attached File containing data points concerning RXAPI sizes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3535652&group_id=119701 |