 | | From: | David Kleinman | | Subject: | Memory drain from reports | | Date: | Wed, 12 Jan 2005 16:25:24 -0500 |
|
|
 | 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 from reports | | Date: | Mon, 17 Jan 2005 16:53:54 -0500 |
|
|
| Can this be corrected by rendering reports in a separate session? Any idea how to do this?
David Kleinman Wrote:
> 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: | John Fried | | Subject: | Re: Memory drain from reports | | Date: | Mon, 17 Jan 2005 10:30:46 -0500 |
|
|
| David,
I know this was a regression in 2.21 that was supposedly fixed in 2.5 (I
haven't tested it personally). I would strongly suggest that you post this
(with details like Windows version, etc.) to the bug reports n/g. If it's
not fully fixed, dBI needs to know about it. I have several large clients
still running apps with dB2K because of this memory drain problem.
John
David Kleinman wrote:
>
> 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.
|
|
