|
|
 | | From: | David Kleinman | | Subject: | Memory drain when closing reports | | Date: | Mon, 17 Jan 2005 11:08:17 -0500 |
|
|
 |
Below I have attached the entry I made in the reports newsgroup regarding memory loss from rendering reports. I am running under Windows XP and NT. As stated the problem has been greatly reduced in version 2.5 from version 2.21, but it still exists. I runn several hunderd individual reports and keep a log database to track memory usage. The memory fluctuates, but averages about 100 bytes per report over several hundered generated.
==================================
From my post is the ""Reoprts" newsgroup:
I'm running a great number of individual reports throughout the day. I find that with each report I lose a little more available memory. The memory loss is a about 100 bytes per report under dBase version 2.5. This is a lot better than running under version 2.21 where memory loss was about 800 bytes per report.
Does anyone have any idea what is causing the loss and how to possibly recover the available memory without terminating the program? There must be some incomplete clean-up that dBase does when a report object is released.
|
|
| | From: | Marty Kay | | Subject: | Re: Memory drain when closing reports | | Date: | Tue, 18 Jan 2005 12:30:01 -0500 |
|
|
| Hi David,
Can you provide a test case for this.
How are you tracking memory?
Thanks,
- Marty Kay (dBI) -
> Below I have attached the entry I made in the reports newsgroup regarding
memory loss from rendering reports. I am running under Windows XP and NT.
As stated the problem has been greatly reduced in version 2.5 from version
2.21, but it still exists. I runn several hunderd individual reports and
keep a log database to track memory usage. The memory fluctuates, but
averages about 100 bytes per report over several hundered generated.
>
> ==================================
> From my post is the ""Reoprts" newsgroup:
>
> I'm running a great number of individual reports throughout the day. I
find that with each report I lose a little more available memory. The memory
loss is a about 100 bytes per report under dBase version 2.5. This is a lot
better than running under version 2.21 where memory loss was about 800 bytes
per report.
>
> Does anyone have any idea what is causing the loss and how to possibly
recover the available memory without terminating the program? There must be
some incomplete clean-up that dBase does when a report object is released.
|
|
| | From: | David Kleinman | | Subject: | Re: Memory drain when closing reports | | Date: | Tue, 18 Jan 2005 16:36:36 -0500 |
|
|
| Hi Marty,
I generate invoices one at a time from a table as they become needed. After each invoice report is released, I log memory() to a event_log table. The reason I was doing this was that after about 200 invoices, my application simple shutdown (window closed) without generating an error message. I started putting break points into my program to try and resolve at what poiint the program closed.
If you want me to send you my application and sample data let me know - or you can give me a call.
David Kleinman
Marty Kay Wrote:
> Hi David,
>
> Can you provide a test case for this.
> How are you tracking memory?
>
> Thanks,
>
> - Marty Kay (dBI) -
>
>
> > Below I have attached the entry I made in the reports newsgroup regarding
> memory loss from rendering reports. I am running under Windows XP and NT.
> As stated the problem has been greatly reduced in version 2.5 from version
> 2.21, but it still exists. I runn several hunderd individual reports and
> keep a log database to track memory usage. The memory fluctuates, but
> averages about 100 bytes per report over several hundered generated.
> >
> > ==================================
> > From my post is the ""Reoprts" newsgroup:
> >
> > I'm running a great number of individual reports throughout the day. I
> find that with each report I lose a little more available memory. The memory
> loss is a about 100 bytes per report under dBase version 2.5. This is a lot
> better than running under version 2.21 where memory loss was about 800 bytes
> per report.
> >
> > Does anyone have any idea what is causing the loss and how to possibly
> recover the available memory without terminating the program? There must be
> some incomplete clean-up that dBase does when a report object is released.
>
>
|
|
|
