All:
Does the next version of SM address the CPU spins that I am experiencing ?
Thanks
Rodney

Rodney Sampson wrote:
Miles:
Didn't seem to be an issue till someone introduced "Akamai Netsession" to the mix. I deinstalled it and things went downhill from there and I'm just reading mail no browser involved.
  But that may explain one of the errors that I'm getting
Timestamp: 7/5/2015 3:39:50 PM Error: TypeError: browsers[i] is undefined Source File: chrome://navigator/content/tabbrowser.xml
Also having browser issues just reading web pages (most will hang)
Is there any fix for this wait issue, I've reduced the Network connection timeout to 20 secs.
Thanks
Rodney

Miles Fidelman wrote:
Tell me about it. I think the problem has to do with handling multiple HTTP calls in parallel. There's this proliferation of pages that contain tons of JavaScript, make tons of calls to load libraries, cookies,
trackers, etc. - a lot of which seem to come from overloaded servers.
And while it's waiting, SeaMonkey seems to freeze ALL it's tabs and windows.
Miles Fidelman

Rodney Sampson wrote:
Still waiting for ideas...
Having to kill & restart SM a dozen times a day is getting quite old...
I'm also considering abandoning SM for Thunderbird, any got-ya's
lurking ?
Thanks

Rodney Sampson wrote:
Have sent 3 crash reports this morning just reading email
Any clues ? Did MS patch something that SM is allergic to ?
Thanks

Rodney Sampson wrote:
Deinstalled SM & Reinstalled, no change
Repeating...

Rodney Sampson wrote:
Lee wrote:
On 7/5/15, Rodney Sampson<[email protected]>  wrote:
Lee wrote:
On 7/4/15, Rodney Sampson<[email protected]>  wrote:
Lee:
      I've been seeing this error regardless of whether or not I
have a
proxy used.
      Clues ?
The PAC file is Proxy Auto Config file, so SeaMonkey shouldn't be
trying to load a PAC file if it's set to directly connect to the
Internet.   So try this
     Edit / Preferences / Advanced / Proxies
and select
     Direct connection to the Internet
This is what I've been using, yet the proxy message is still
present...
Maybe SeaMonkey looks for the PAC file even if it isn't going to
use it???

Try enabling automatic proxy config, removing thehttp://sourceforge
... URL info and setting it back to direct connection.

Lee



Exit SM, start it again, check that Direct connection to the
Internet
is still set (if no we need to figure out how it's being
cleared) and
then see if the error loading PAC file still shows up in the error
console

Regards,
Lee



Thanks
Rodney

Lee wrote:
On 6/30/15, Rodney Sampson<[email protected]>  wrote:
All:
       Starting with the error console, can anyone tell me
what this
error
means ?
PAC file failed to install from
http://sourceforge.net/projects/ijbswa/files/Win32/3.0.23%20%28stable%29/
       Figured I'd start eliminating 1 error at a time...
Edit / Preferences / Advanced / Proxies

If you're using [or want to use] Privoxy you should have
      Manual proxy configuration
checked
      127.0.0.1
as the Proxy and
      8118
as the port.  & Privoxy has to be running or you won't be able
to get
to the Internet

otherwise
      Direct connection to the Internet
should be checked.

I'm guessing you have
      Automatic proxy configuration URL
checked & something like

http://sourceforge.net/projects/ijbswa/files/Win32/3.0.23%20%28stable%29/
in the URL field

Regards,
Lee

Cool 1 down...
Failed to load native module at path 'C:\Program Files
(x86)\SeaMonkey\components\xpcomsample.dll': (80520012) <unknown;
can't get error from NSPR>
Timestamp: 7/5/2015 3:39:26 PM  Error: uncaught exception: 2147942487
Timestamp: 7/5/2015 3:39:50 PM  Error: TypeError: browsers[i] is
undefined Source File:chrome://navigator/content/tabbrowser.xml Line: 331
Here's the next 3 errors...
Thanks



_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey





_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to