"hawker" <[email protected]> wrote in message news:[email protected]... > On 10/4/2013 5:30 AM, Desiree wrote: >> "David E. Ross" <[email protected]> wrote in message >> news:[email protected]... >>> On 10/3/13 4:57 AM, Desiree wrote: >>>> On XP Pro, that stupid Flash plugin container tried to start as Sea >>>> Monkey >>>> 2.21 was starting! It should not start unless I decide to start Flash >>>> Player >>>> which is controlled by a toggle switch and can't start until I give >>>> permission. Plus, none of the tabs that were loading have any Flash >>>> Player >>>> video on them and the Proxomitron blocks all ads that might use Flash. >>>> So, >>>> I told Process Guard to deny Flash Plugin container from running. I've >>>> never >>>> had a problem doing that in the past but I guess 2.21 won't allow one >>>> to >>>> control Flash Player as when I did that Sea Monkey froze and then >>>> crashed. >>>> >>>> I tried starting it in Safe Mode and same thing, it is not allowed to >>>> load >>>> Flash Plugin container so it freezes and crashes. I thought Safe Mode >>>> disabled plugins? Evidently not...so what is the purpose of Safe Mode? >>>> >>>> I updated Flash Player recently and for some stupid reason that >>>> activates >>>> it >>>> on Fx and SeaMonkey disregarding my plugin settings where I had it >>>> disabled. >>>> If I disable it then SeaMonkey should not crash because Flash plugin >>>> container two processes won't try to load. So, if I can start >>>> SeaMonkey >>>> offline would that work so I could disable Flash plugin? >>>> >>>> (The real problem is that no browser should automatically grab a >>>> plugin. >>>> I >>>> remember when they did not and they still should not do that). >>> >>> Windows XP Home Edition SP3 >>> Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 SeaMonkey/2.21 >>> Flash 11.7.700.224 (11.7 r700(224)) >>> >>> I used Ctrl-Alt-Del to view the Windows Task Manager. While >>> plugin-container.exe appeared, it was not consuming any CPU resources, >>> only memory. Note that plugin-container.exe is also used for plugins >>> other than Flash. >>> >>> Safe Mode only disables extensions, not plug-ins. I think it was a very >>> bad decision when the Mozilla developers started referring to "add-ons" >>> as including both; this has led to extreme confusion among end users. >>> >>> I control Flash with the Flashblock extension from >>> <http://flashblock.mozdev.org/>. >>> >>> -- >>> David E. Ross >>> <http://www.rossde.com/> >> >> I have a powerful CPU (for the age of this computer). I am not concerned >> about plugin container 2 processes using CPU. I do NOT want plugin >> container >> processes eating memory and those processes eat a LOT of memory. The one >> and >> only drawback (besides the fact the machine weighs 50 pounds and is >> really >> heavy for me to pick up) to this otherwise fantastic (when new and still >> nice today) gaming computer has been a bug with the nVidia motherboard >> which >> limits the RAM to 2GB (and, of course, 32bit Windows XP Pro limits the >> RAM >> to slightly over 3GB if I could add RAM). I can't see anyone on XP using >> SeaMonkey now because it eats too much RAM with unnecessary stuff like >> these >> two processes running all the time. Also, I run virtual machines on this >> computer and I constantly have to watch the ram usage. It's the reason I >> bought a new Windows 8 computer last November with 16GB RAM which is more >> than I need. >> >> I agree putting plugins on the Addons tool page was foolish but even I >> who >> have used Mozilla browsers since 2001 (Netscape before that) knew plugins >> weren't addons but then they were put on Addons page and wondered about >> changes and that plugins were now like extensions, ergo, they should be >> disabled also when using safe mode. >> >> > > It sounds like your real issue is not Seamonky but you are limited to > 2GB. Modern XP SPIII with modern apps/drivers/TSRs etc idles at about > 1.25GB so you really need that 4GB limited to 3.5 for XP to run right. 2GB > is not quite enough anymore - barely not enough but not enough. If you > could get around that this would be a non issue. Are you sure there isn't > a BIOS update for your MB to fix that? > There was never any way to fix the problem. It was the first in the XPS series. The next year's XPS 700 fixed it. Besides, it doesn't run XP Pro SP3. I put that on a virtual machine when it came out and didn't like it and reverted the virtual machine to SP2. The host computer I never upgraded to SP 3. With Process Guard it does not need SP 3 for security reasons. So, it can run on 512MB RAM if necessary like XP Pro SP 1 that 1 had before the SP 2 machine could do. The problem was running virtual machines on it (especially Vista Ultimate that needs a lot of RAM).
To me, the problem is that I will not run SeaMonkey on any computer if I cannot keep those stupid plugins from running all the time (but I should be able to disable Flash on SeaMonkey. It is just principle that makes me not want to allow those plugins to run even long enough to keep SeaMonkey from crashing before I can disable Flash which will stop the plugin container from running). I use Fx 17.0.9 ESR on my Windows 8 computer. I don't have to fight with those stupid plugins. I keep Flash disabled all the time on Fx on Windows 8. I better not have a problem when Fx upgrades in January to ver 24 with those plugins or I'll either not upgrade or I'll revert to ver 17. If I need Flash on my Windows 8 machine, I use IE 10. I would NEVER RUN FLASH on a Mozilla browser that requires those stupid plugins that run all the time and eat a lot of RAM. On Windows 8, I have plenty of RAM but it is the the principal of the thing. What in the world was Mozilla thinking of when they decided to use those stupid plugins container for Flash? Flash is irrelevant anyway except for a few speed tests. I use HTML5 if youtube, or whatever video won't play in HTML5, then I don't care to see it. I have always detested Flash from 1999 on. I'd rather never watch any videos if I can only see them in Flash. I have Flash ONLY for speed tests and Flash is horrible for speed testing (Java is far more accurate) but my ISP requires it. I should be able to have Flash on Opera ONLY. Opera (12.15...not the abomination version 15) doesn't have those silly Flash plugins and it is very easy to keep a tab open all the time to Opera's plugins where I enable/disable Flash frequentily with simple ease. SeaMonkey and Fx should be like that. Even on IE 10 it is very simple and fast to enable and disable Flash (in the browser -not with some third party extension) and there is no stupid plugins running all the time. Only Fx and now SeaMonkey make a complete mess of Flash. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
