Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Running Out of Memory
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Divers
Thread ID:
00347130
Message ID:
00348753
Vues:
24
>Gentlemen,
>Here is another twist on the 'Memory Leak' theme.
>
>
>We have automated a process, through VFP6, whereby we produce reports (many with images) in batches of roughly 10 reports at a time, zip them up together, attach them to an e-mail & send them on their way. In total, there may be as many as 1000 reports "printed" as PDF files (Acrobat 4.0), sent in a batch overnight. We have found that, after the production of over 100 reports, the fox reports start dropping images, Although the reports will continue to show text properly.
>
>We have devised a process to capture current memory handles and the amount of "used memory" as the batch is handled. We have found that, indeed, used memory builds throughout the process.
>
>We suspect that this time Acrobat is the culprit, for the following reasons:
>1. And unlike the leak that occurs in report previews, the system does not jam up and throw error messages at us.
>2. Fox continues to produce reports with everything, except the images. Images are .jpg ranging from 50k to 250k... and size does NOT matter.
>3. In the Preview Leak, we were able to remedy by closing VFP and opening it back up. In this leak, closing VFP does not clear memory.
>
>I would be interested in hearing from anyone who has had similar problems with Acrobat & Fox, especially if they have an idea for solving the problem.
>Thanks.
>
>
>>Report preview has a memory leak in it. It was stated that this was fixed with VFP6/SP3, but that is incorrect. It's still there.
>

This doesn't really surprise me. We've got some kind of problem with systems that have had Acrobat 3 on them after they've been upgraded to Acrobat 4. Some of these systems get "insufficient memory" & "failure to create object" messages running VFP apps.

I can't exactly pin it on the Adobe drivers just yet, but they're real high and lonely on the suspect list.

>>See MS QB article Q216587 on this. It states:
>
>>"...The Visual Studio 6.0 Service Pack 3 readme erroneously lists this bug as being fixed. Service Pack 3 did not fix this bug."
Fred
Microsoft Visual FoxPro MVP

foxcentral.net
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform