Not sure about any relationship but I don't have any problems with
running Mozilla becoming frozen like that (though NS 4.61 does it alot).
I am assuming you are socksified, which socks server are you going
through(I assume socks1). In Boulder I use socks2 and am using that one
here in Toronto where I am this week. You might try editing your
socks.cfg file and trying different socks servers to see if it is
related to socks at all. Also you might rename the socks.cfg file and
try just internal sites and see if you have the same problem (assuming
you haven't cause it not mentioned here).
Haven't had it lock the system up if I leave it running but I don't
typically do that either cause I work nights and would have it up for
12+ hours then but have to close it down to refresh email any time I get
new email. I have left one of the versions running during the day
after I left and it shut down fine when I came in but don't remember
which version that was as it has been awhile so can't attest to current
version.
Andy
DuaneC wrote:
> I'm seeing some very strange behaviour in 0.9.1
>
> First, I'm behind a crappy SOCKS connecting here at IBM-RTP. I set Moz
> up to "direct" connect as none of the SOCKS or AUTOPROXY functions
> seem to work.
>
> The problems are:
>
> 1) during some fetches/online action Moz will become frozen for QUITE
> a long time (minutes) and I usually can switch and kill it from the
> task list.
>
> 2) after Moz has been running for a long time (overnight) and I shut
> it down, it will freeze the system (no graphic updates at all!) for a
> minute or so and peg the CPU. Eventually this returns and Moz exits.
>
> I think these problems may be "related".
>
