On Thu, Jan 20, 2000 at 04:04:38PM +0100, [EMAIL PROTECTED] wrote:
> > Events & ioevents are never deallocated. If you think this is a
> > problem then I can provide a function to deallocate everything on the
> > freelist. However, I doubt that this is worthwhile.
>
> Hm, what does it mean? If it does not result in an ongoing memory allocation while
> thousands and thousands of IO watchers are installed and cancelled - as I wrote
> before, the servers and clients should run for very long periods -, this will be no
> problem from my point of view.
Yes, that is what I expect. The only way to cause lots of events to be
allocated is to generate them without servicing them. As they are
serviced, the memory is recycled.
> Just to understand it better - Events and ioevents are collections of all (specific)
> events detected while a loop is running?
Yes. Only pending events use memory.
> I think it is real improvement, but a few minutes ago I had to recognize that the
> server grows again (after a period of constant memory allocation) ... I wished it
> would not, really. I will implement the checks. But, of course, my be there's a
> fault in my own code.
At least you have some assurance that Event is no longer causing the
problem. Ugh.
--
"Does `competition' have an abstract purpose?"
via, but not speaking for Deutsche Bank
