On Mon, Jul 6, 2009 at 3:40 PM, Rick McGuire<object.r...@gmail.com> wrote:
> I checked a few additional items, and this merely confirmed my > suspicions. The initial object heap allocation is 8Mb, plus the > restored image is close to 1Mb. That's 9Mb of memory that we allocate > up front, but the taskmanager is only showing around 4Mb of memory in > use. The growth tops out at roughly 8Mb more than the initial size, > which is a very consistent set of numbers. Rick, I agree here. It is not a memory leak, if it hits an upper limit and then stays there no matter how much longer you run the program. This behavior is very consistent with what we've seen before. It was Lee who had opened a bug about a memory leak and supplied a test program. When I investigated, I saw it wasn't a memory leak because it topped out. In fact, that was when I set up the performance counters I mentioned earlier. Running his program overnight using the counters showed conclusively that memory never went over that one peak, that was hit very early in the run. Like after 10 minutes. The it ran for 12 hours never going over the peak. The thing is, I thought I saw the non-debug version of this sample program go over 24 MB, before I switched over to use the debug libraries. I'll run the non-debug version over-night, but I think it will just confirm there is not a leak. -- Mark Miesfeld ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/blackberry _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
