Hi All,
I'm running Crw 9 sp 2 inside VB6(sp5) with SQL2000 back end on OS's WinXP, Win98, WinME, Win2k.
I'm finding huge, huge memory leaks occurring on client machines when they run a report.
When I first access our application it may be using, say 30mb of RAM (in Task Manager in the Mem Usage column). Then I go and run a report. The report will be large and it might add another 30mb of mem, so total mem usage is 60mb.
Then I quit the report, mem usage only drops back to 56mb. So I run the report again, mem goes up to 90mb, quit the report and it says I have 86mb. As you can imagine, a client machine with 128mb of ram will crash or at start paging very quickly. The mem usage is supposed to drop back to the original 30mb.
We are concluding that the report is not dropping the record set, just keeping it in memory.
Interestingly this has only occurred in CRW 9 SP2. When we were running CRW 8.5 this issue was not occuring. Does anyone know if there is a specific issue concerning releasing memory when running reports, or is it just a (another) bug in Crystal?
Cheers
I'm running Crw 9 sp 2 inside VB6(sp5) with SQL2000 back end on OS's WinXP, Win98, WinME, Win2k.
I'm finding huge, huge memory leaks occurring on client machines when they run a report.
When I first access our application it may be using, say 30mb of RAM (in Task Manager in the Mem Usage column). Then I go and run a report. The report will be large and it might add another 30mb of mem, so total mem usage is 60mb.
Then I quit the report, mem usage only drops back to 56mb. So I run the report again, mem goes up to 90mb, quit the report and it says I have 86mb. As you can imagine, a client machine with 128mb of ram will crash or at start paging very quickly. The mem usage is supposed to drop back to the original 30mb.
We are concluding that the report is not dropping the record set, just keeping it in memory.
Interestingly this has only occurred in CRW 9 SP2. When we were running CRW 8.5 this issue was not occuring. Does anyone know if there is a specific issue concerning releasing memory when running reports, or is it just a (another) bug in Crystal?
Cheers