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 go for some trouble.
Craig
NoOp wrote:
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 thousand other variables. It might also be some shitty
java
script only activated when the website sees a never Firefox version or even bad
browser sniffing.
No countless tabs, often just one. I don't run the browser continuously.
I suggest using a script and adblocker if you don't already do so. If it still
freezes it should always do it on the same pages then.
uBlock Origin. Noscript became impossible, making things work that I needed to
have
work on a specific site became a time-wasting game.
And if you did go back from 2.51 your profile might have corruption too. Check
for
indexDB or storage errors on startup. If you see some you need to clean it
first.
I haven't been playing pioneer, lately, and no explicit startup errors.
Just back up your profile and try it. It might not work for you or it might be
better. You won't know until you try it out.
OP asked if 2.49.1 ever froze. It has, but not often enough to make it
unusable. It
can go for prolonged periods without crashing at all. It has crashed under
stress...for example, SM 2.49.1 popped like a soap bubble when I tried sending a
particularly enormous email loaded with animated GIFs. Weirdly, that happened
both
when I attached the files AND when I then tried sending by reference. (In the
latter
case the email DID at least go through.) But it has also crashed when absolutely
nothing out of the ordinary is going on, when it will go into its "white out"
routine, as described, and I have to kill and restart. No rhyme or reason I've
been
able to spot. Just a guess: script! I will remember your backup and indexDB
advice.
Craig
Ditto.
Unfortunately it typically doesn't crash, it just freezes so no new
crash reports are generated.
My last crash on 2.49.1 was on 11/15 & that was caused by
hang | NtUserMsgWaitForMultipleObjectsEx | user32.dll@0x5d3ed
That seems to have been caused by a plugin:
plugin (web) Foxit PhantomPDF Plugin for Mozilla Version: 2.2.7.818
Filename: npFoxitPhantomPDFPlugin.dll
Which was removed following the crash. SM 2.49.1 Windows has frozen at
least 4 times since. When I look at the Windows task manager it just
shows 'Not Responding'.
I'll see if I can get some repeat site/page to troubleshoot... in the
interim it's Thunderbird & Other Browser time (on Windows - linux is
just fine) until I can figure out the issue. Thanks for all the responses.
<snipped>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
