Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Mozilla Plugin Check page crashes with NS_ERROR_XPC_BAD_OP_ON_WN_PROTO

  • 1 odgovor
  • 24 imaju ovaj problem
  • 1 prikaz
  • Posljednji odgovor od 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?

Svi odgovori (1)

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.