On 12/10/2002 at 10:47 AM Mark Crispin wrote: >On Tue, 10 Dec 2002, Shawn Walker wrote: >> Then how does one get cclient to free the memory after it retrieve a VERY >> large message from the server? I debugged into cclient saw how the >message >> is being stored in memory and how to free it and the only way was to run >> the garbage collector. > >What do you mean by "VERY large"? > >Whenever you run the garbage collector, you destroy the entire cache, >which means that c-client is forced to re-fetch any data that it needs >again. Unless you mean at least "tens of megabytes" by "VERY large", you >are causing more harm than good by doing so. > >And even if it is that big, what if the user references it again? > >Note that when you expunge a message, any cache associated with that >message is freed. > >Memory is cheap. Use it. > >-- Mark --
That is the "problem". I have had several customers running low on resources when the application was downloading a very large INBOX folder (the folder contains several thousands messages with very large messages that contains attachments). The user was getting memory getting low on the windows machine. I was able to recreate the problem what the customers was having and it was a problem. I had to get cclient to free the memory to keep that from happening. Shawn
