From: worldoff9908@gmail.com   
      
   Mike Spencer wrote:   
   > I'm seeing an increased number of crashes on 2.53.20, always when   
   > javascript is on.  Google search now refuses to do anything without js   
   > enabled and I try to rely on other search sites but still occasionally   
   > turn on js and try to use Google Advanced.   
   >   
   > I'm seeing frequent crashes with Google and elsewhere but also failure   
   > to correctly handle Google's Prove You're Not A Robot thingy.   
   >   
   > Do the "crash reports" Seamonkey claims to be sending "home" have any   
   > real benefit?  Are they contributing substantially to reducing or   
   > eliminating javascript-related crashes?   
   >   
   > I might add that the one site where I always (and of necessity)   
   > enable js works as expected every time.  That's very good!   
   >   
      
   A couple of thoughts...   
      
   Is there any reason that you haven't upgraded to 2.53.21? I don't know   
   if that will fix any of your problems, but it's good to make sure that   
   you're on the most current version.   
      
   My suspicion is that you're hitting something that's fairly deep in your   
   user profile, and not an inherent issue with Seamonkey.  Thus, one thing   
   to try would be a restart in Safe Mode (Help -> Restart with add-ons   
   disabled), as well as seeing what happens when you try interacting with   
   a different profile, where all the settings are defaults, and no   
   personal preference settings.  In my own use, I do keep a profile titled   
   "bare metal", and it's good for troubleshooting these kinds of issues,   
   where I can determine if odd behavior is something general to Seamonkey,   
   or if it's related to my own configurations of Seamonkey.   
      
   I'm not sure if Seamonkey is really well suited to constantly enabling   
   and disabling javascript.  To me, a better approach is with NoScript,   
   where there's a lot more capacity of enabling/disabling (whether   
   permanently or one time) individual scripting hosts. NoScript allows for   
   a much more granular approach, and not having to do all or nothing with   
   scripting permissions.   
      
   In my own usage of NoScript, I default everything to disabling   
   scripting, and then where I'm willing to take the effort to whitelist   
   hosts as needed.  There are some hosts that I encounter frequently   
   enough and trust that I'm willing to permanently whitelist, and there   
   are others that I distrust enough that I've been able to set them to   
   permanent blacklisting (where using NoScript's capacity of temporarily   
   whitelisting everything at a particular site will not enable the   
   permanently blacklisted sites).   
      
   With Google-related sites, I leave all of those default blacklisted, and   
   will enable them as seems necessary. I know that google.com is necessary   
   for sites that allow searching with Google (both google proper, as well   
   as third party sites that offer searching and use Google), as well as   
   Google's CAPTCHA. Sometimes (but not always), a site that has content   
   cached ago Google may require enabling of gstatic.com, and that may   
   include fonts.gstatic.com.  Other google-related sites, such as Google   
   Tag Manager or Google APIs are hit-and miss. The only Google site that   
   I'm confident of blacklisting permanently is Google Analytics, which I   
   know is a way of reporting activity to site owners (as well as Google).   
   I don't care about cooperating with site owners, and I've found that   
   permanently blocking Google Analytics is a zero-loss proposition.   
      
   I won't suggest that any of these will necessarily make crashes go away,   
   but they may help you identify where problems are originating from. If   
   you don't find a solution otherwise, it may be preferable to build up a   
   new profile from scratch.  That's relatively easy to do if you're   
   accounting for just the browser, but will be more effort if you also   
   have to transition your mail, especially if you have POP connections.   
      
   Smith   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)