On 5/24/2015 2:01 AM, A Williams wrote: > Miles Fidelman wrote: >> Thee Chicago Wolf [MVP] wrote: >>> On Wed, 22 Apr 2015 16:29:15 -0700, "David E. Ross" >>> <[email protected]> wrote: >>> >>>> On 4/22/2015 4:02 PM, Miles Fidelman wrote: >>>>> Is it just me, or are other folks experiencing frequent hangs in the >>>>> Seamonkey browser? >>>>> >>>>> It seems like half the web pages I visit these days lead to spinning >>>>> beachballs, 100% machine load, and often, the need to force quit and >>>>> restart. >>>>> >>>>> Miles Fidelman >>>>> >>>> See my message "SeaMonkey and Yahoo" in this same newsgroup. The >>>> problem seemed to disappear this afternoon. >>> I'm running SM 2.33.1 and never have lockups or freeze. I have an old >>> Latitude E6400 with 2GB RAM and NVidia 160M. Not exactly modern but >>> not slow. What SM are you running? Have you defragged lately? Have you >>> done a Checkdisk lately? >>> >>> >> User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:36.0) >> Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 >> Build identifier: 20150321205436 >> >> Defrag - no; generally not something one does on Macs. Checkdisk, no >> (good idea, will do it), smart diagnostics, yes - the disk seems to be >> healthy. >> >> >> >> > > > Having done a search of my postings here, I have had this problem since > at least September 2013. I run Seamonkey under Linux and under Windows > but afaik this problem only affects Linux. Of course I have a > process-monitor running under Linux so maybe I would not notice if it > happened under Windows. > My machines all have at least two cores so Seamonkey is still > responsive. Closing browser windows, tabs, anything else makes no > difference once the loop has started - in the end Seamonkey has two > processes left: > - /usr/bin/seamonkey > - /usr/lib64/seamonkey/seamonkey-bin > The second one is running one processor at 100% and that is the one I > have to kill. > If I do not kill it, > - I can't restart Seamonkey in that session > - Seamonkey restarts automatically on a new session. > > Unfortunately opensuse build Seamonkey with the --disable-crashreporter > (and --disable-debug) flags, otherwise looking at the crash-report would > possibly indicate what it thought it was doing at the time. >
Windows 7 Ultimate SP1 (x64) SeaMonkey 2.26.1 I see this frequently with Yahoo sites and sometimes this with other sites. I attribute the problems to buggy scripts used by frequently updated Web pages. If I encounter such a problem, kill SeaMonkey, and then wait about an hour before trying an afflicted site, the problem usually is resolved, possibly because the page has been again updated. -- David E. Ross I am sticking with SeaMonkey 2.26.1 until saved passwords can be used when autocomplete=off. See <https://bugzilla.mozilla.org/show_bug.cgi?id=433238>. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
