560843 - jetpack breaks platform

Status: RESOLVED INVALID

(Core :: XPCOM, defect)

Description

[John J. Barton]

Attachment: a buggy extension

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.5pre) Gecko/20100420 Namoroka/3.6.5pre

1. Install https://addons.mozilla.org/en-US/firefox/downloads/latest/12025/addon-12025-latest.xpi?src=search
2. Install bug.xpi attached
3. Restart browser. Exit
4. Restart browser with -jsconsole
In the Error Console you will see (along with normal errors):
Error: Components.classes['@johnjbarton/testcomponent;1'] is undefined
Source File: chrome://bug/content/overlay.xul
Line: 6

This is incorrect.

5. FF > Tools > Addons > Extensions > Jetpack > select disable
6. Restart.

Then you will see in the Error Console:
Error: First Bug is that this does not show up
Source File: file:///C:/Users/johnjbarton/AppData/Roaming/Mozilla/Firefox/Profiles/bug/extensions/[e-mail]/components/testComponent.js
Line: 2
Error: uncaught exception: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXPCComponents_Utils.import]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: file:///C:/Users/johnjbarton/AppData/Roaming/Mozilla/Firefox/Profiles/bug/extensions/[e-mail]/components/testComponent.js :: <TOP_LEVEL> :: line 5"  data: no]
Failed to load XPCOM component: C:\Users\johnjbarton\AppData\Roaming\Mozilla\Firefox\Profiles\bug\extensions\[e-mail]\components\testComponent.js
Error: Components.classes['@johnjbarton/testcomponent;1'] is undefined
Source File: chrome://bug/content/overlay.xul
Line: 6
These are the correct outputs.

Comment 1

[John J. Barton]

Using 
https://addons.mozilla.org/en-US/firefox/addon/151809 
in place of jetpack prototype I verified that this bug also applies to jetpack SDK 0.3

Comment 2

[Nickolay_Ponomarev]

The first time after extension installation (when the XPCOM autoregistration happens) you see 3 errors, on subsequent restarts you get only the last one about component failed to register.

Try:
7. Exit. Restart browser with -jsconsole
(like you did after installing jetpack in steps 3-4)

This is not related to jetpack at all. We just don't try register components over and over, even if the first attempt failed.