User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20090729 Firefox/3.5.2 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20090729 Firefox/3.5.2 ( .NET CLR 3.5.30729) Hello, In 2 years + of using Firefox I've never had major issues with it, and its been a refreshingly smooth ride after long experience with the many hazards of IE. However, recently after updating to the latest v. I've had pretty much the worst browser experience of my life, which has made using the program not just aggravating, but pretty much unusable. Apparently its all down to 'plugin-container.exe'; FF continually crashes, and a box pops up naming this process as the culprit. Often the entire system needs a reboot to get back to normality. The workarounds here dont work for me: http://support.mozilla.com/en-US/forum/1/707504 http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Disabling_crash_protection In my exasperation with it, I've reinstalled an old version (3.5.2), but this is hardly ideal, seeing how a main part of new versions is to fix security holes. Would appreciate some assistance on this. Sincerely, Kay Reproducible: Always Steps to Reproduce: 1. Boot FF 2. Browse web normally 3. Tear hair out Actual Results: Browser lock up; often system lock up.
2f163d6a-2cf1-4c23-a05d-0c1296a3bc80 7/1/2010 dfb2988a-4e84-48a9-9a52-c077b3ac3f2c 7/1/2010 31356f42-9276-4952-97be-51888d27846a
sorry for the delay, it sounds like those reports weren't submitted, could you try clicking on them to cause them to submit? once you've done that, you should see different id's which you can paste here. thanks.
Alright. Well, that's odd because I got those codes from using the Mozilla url that details bug reports submitted, so perhaps the problem is non-reception? Anyway, the situation has changed for the better - that error message hasn't come back in the last 5 days or so. Not sure if this is down to Mozilla tinkering, or the removal of an extremely well-hidden rootkit called 'Alureon H' which had been lurking on my rig. I'll let you know if it re-occurs, but I guess we can say this one is provisionally resolved. Thanks.
could you please try clicking on them anyway? :)
Ok, here's the respective crash IDs:- ID: 661db734-a313-4fe0-9abc-90e4b2100722 ID: 7b4eaddd-fc4d-4c5d-bbc9-876e42100722 ID: 10a89837-bc50-40f3-9f9a-fa6882100717 Enjoy! ;) Thanks, Kay