David E. Ross wrote:
On 9/25/12 11:04 AM, Bob Fleischer wrote:
Actually, it doesn't kill the process, but all windows disappear and
SeaMonkey apparently consumes no resources (other than the memory it is
already using).
Bob
Windows XP SP3
Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120909 SeaMonkey/2.12.1
I have no problem in viewing the LA Times home page at
<http://www.latimes.com/> or navigating through that Web site.
I have seen many reports about problems with SeaMonkey 2.12.1. One
thing in common to most of those problems is with the SeaMonkey that has
the UA string
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120909
Firefox/15.0.1 SeaMonkey/2.12.1
I am beginning to suspect either a Windows 7 bug or a problem with the
way SeaMonkey interfaces with Windows 7.
I have no problem with that page or any of the others that have been
reported and I'm on Windows 7 with that UA string:
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0)
Gecko/20120909 Firefox/15.0.1 SeaMonkey/2.12.1
I think most of the problems people are having are caused by bad
plugins, extensions, or antivirus programs and not SeaMonkey or their
OS. It would save a lot of time if everybody would try safe mode
before assuming they have a problem with the browser.
--
Jim
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
