If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Solutions on Mozilla site for 'plugin-container.exe' not working

RESOLVED WORKSFORME

Status

()

Firefox
General
--
critical
RESOLVED WORKSFORME
7 years ago
7 years ago

People

(Reporter: tiakapan, Unassigned)

Tracking

3.6 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) 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:1.9.1.2) 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.
(Reporter)

Updated

7 years ago
Version: unspecified → 3.6 Branch

Comment 1

7 years ago
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
(Reporter)

Comment 2

7 years ago
2f163d6a-2cf1-4c23-a05d-0c1296a3bc80	7/1/2010	
dfb2988a-4e84-48a9-9a52-c077b3ac3f2c	7/1/2010	
31356f42-9276-4952-97be-51888d27846a

Comment 3

7 years ago
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.
(Reporter)

Comment 4

7 years ago
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 5

7 years ago
could you please try clicking on them anyway? :)
Resolution: FIXED → WORKSFORME
(Reporter)

Comment 6

7 years ago
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

Comment 7

7 years ago
filed bug 581184 and bug 581185

the other one is missing its corresponding bit, not sure why.
You need to log in before you can comment on or make changes to this bug.