18-Dec-00 Matt Sealey wrote:
>> Sometimes.... well, oftenish... when I try to quit Miami I'm told that
>> I can't because V's network and file server is still running.
>
> Even after you ask Miami to try and kill them? Both V and V's net
> process should exit when the IP stack tells them to..
Oh yes, they _should_ - that's the problem.. .)
I've had this behaviour with V3 for ages (as far as we've had a V3..), every
now and then. V3.2.13 hardly ever does that for me, but the earlier betas (as
well as the release version) did it more often. The new alpha version for some
reason has got worse from the V3.2.13 version.. :/
>> _sometimes_ v's network and file server consumes 100% of my cpu
>> time, which is more annoying.
>
> Under what circumstances?
I have never encountered this one. Only problems with the memory usage - memory
not been released.
Hm, I played a little with V3, and it seems to be quite a fool-proof method to
get this situation to close the V3 when it is loading something. But, it also
occassionally does happen even if nothing is being loaded from the web when
closing the program..
--
- Kimmo V��riskoski <[EMAIL PROTECTED]>
_____________________________________________________________________
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
