This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Mozilla Plugin Check page crashes with NS_ERROR_XPC_BAD_OP_ON_WN_PROTO

  • 1 reply
  • 24 have this problem
  • 2 views
  • Last reply by RichardD

RichardD
RichardD
more options

Starting today, I cannot get the Plugin Check page to load. It gets as far as "Checking with Mozilla on the status of your plugins...", and then hangs.

In the error console, I see: Error: uncaught exception: [Exception... "Illegal operation on WrappedNative prototype object" nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)" location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" data: no]

Is this a known problem with the page, or do I have to wipe my profile yet again to get Firefox to work properly?

Starting today, I cannot get the Plugin Check page to load. It gets as far as "Checking with Mozilla on the status of your plugins...", and then hangs. In the error console, I see: Error: uncaught exception: [Exception... "Illegal operation on WrappedNative prototype object" nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)" location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" data: no] Is this a known problem with the page, or do I have to wipe my profile ''yet again'' to get Firefox to work properly?

All Replies (1)

RichardD
RichardD Question owner
more options

OK, via a process of elimination, the problem seems to be caused by Page Speed 1.9; I've disabled the add-on, restarted Firefox, and the plugin check page loads perfectly.

Now I just need to find a way to report the problem to Google.