Ray_Net wrote:
cmcadams wrote on 03-12-17 05:32:
NoOp wrote:
User agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101
Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20171016030418
I switched from Adrian's 2.51 to the released 2.49.1 and on multiple
occasions I've had 2.49.1 freeze on me on Windows (Win 10 - 16GB memory,
same profile that I've been using for years & no, I've not tried with a
new profile yet). It typically happens just when I need it most...
online order checkout, preparing to send important email etc. Note: I've
not experienced the same on the linux version of 2.49.1
Have anyone else had SM 2.49.1 (Windows) freeze on them?
Yes, although I can't come up with anything specific in the way of configuration or
actions to blame for it. Activity grinds to a halt, the twirly twirls, and
memory/cpu activity shoots up and stays there. The window "whites out". Not blank,
just a change in saturation, let's say, to let you know you're screwed. And after
you force-kill SM it can take some time for it to take the hint.
So, it's better to stay with SM 2.46 waiting for the next stable release >
2.49.1 ?
Sadly, I'll have to say yes. 2.49.1 is better than 2.48, but 2.46 was more stable
than either of those. How much risk you'd be running, continuing to use an older
version, I can't tell you.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
