...and back to you, Matt:
>> so far. Go offline. There is no traffic left to handle. Yet AmigaLoad
>> displays the processor load near 100%, with V causing the vast majority.
>> Uhm, why?
>
>The garbage collector has to go through and safely dispose of a large
>heirarchy of objects (the window all the way down to individual links)
>which takes time - both real time and cpu time.
Even hours later? (Yes, I was nuts enough to read all of the comments on
that site. All 218 at that time...)
>I wouldn't trust AmigaLoad as an accurate measure of what V is doing
>either :)
Maybe I should have been a bit more precise. AmigaLoad showed the high
processor load, Scout told me who was to blame. :)
So long, MR
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
