On 12/3/2017 9:19 PM, cmcadams wrote:
> Adding to what NoOp wrote, a little while after my last post I was browsing
> walmart.com and SM 1.49.1 Win began behaving as he described. Unresponsive,
> twirlies
> and intermittent white-outs, all without outright crashing. CPU was high,
> memory was
Adding to what NoOp wrote, a little while after my last post I was browsing
walmart.com and SM 1.49.1 Win began behaving as he described. Unresponsive, twirlies
and intermittent white-outs, all without outright crashing. CPU was high, memory was
at 1.1-1.2GB.
So, walmart might be a place to
On 12/3/2017 11:57 AM, cmcadams wrote:
> Frank-Rainer Grahl wrote:
>> 2.49.1 and now the development build .2 was/is the most stable release I
>> ever used so
>> YMMV.
>>
>> All depends on your browsing habits, if you keep countless tabs open, how
>> often you
>> close the browser and a
Frank-Rainer Grahl wrote:
2.49.1 and now the development build .2 was/is the most stable release I ever used so
YMMV.
All depends on your browsing habits, if you keep countless tabs open, how often you
close the browser and a thousand other variables. It might also be some shitty java
script
On 12/2/2017 6:03 PM, 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
On 12/2/2017 6:03 PM, 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
On 2017-12-02 21:03, NoOp wrote:
Have anyone else had SM 2.49.1 (Windows) freeze on them?
I haven't had this problem. Like you, I'm using the same profile
I've been using for years. Unlike you, I haven't used any pre-release
(alpha, beta, dev, whatever) versions and then gone back down
2.49.1 and now the development build .2 was/is the most stable release I ever
used so YMMV.
All depends on your browsing habits, if you keep countless tabs open, how
often you close the browser and a thousand other variables. It might also be
some shitty java script only activated when the
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
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
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
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
12 matches
Mail list logo
