Closed Bug 608110 Opened 15 years ago Closed 8 years ago

xpinstall/head.js, lines 221, 303 and 321: reference to undefined property installInfo.installs

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: robert.strong.bugs, Unassigned)

Details

Attachments

(1 file)

This was seen in the debug spew with a windows debug build while running browser_auth.js, browser_auth2.js, and browser_whitelist2.js though it might be present in other tests as well.
examples: *** LOG addons.xpi: Starting install of http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/authRedirect.sjs?http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/unsigned.xpi *** LOG addons.xpi: Addon unsigned-xpi@tests.mozilla.org will be installed as a packed xpi *** LOG addons.xpi: Install of http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/authRedirect.sjs?http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/unsigned.xpi completed. JavaScript strict warning: chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/head.js, line 321: reference to undefined property installInfo.installs TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_auth.js | Should only see completed events for started installs TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_auth.js | Completed installs should have no error TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_auth.js | Completed installs should not be appDisabled TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_auth.js | Completed installs should be in the right state JavaScript strict warning: chrome://browser/content/browser.js, line 5807: reference to undefined property installInfo.installs JavaScript strict warning: chrome://browser/content/browser.js, line 5845: reference to undefined property installInfo.installs JavaScript strict warning: chrome://browser/content/browser.js, line 5847: reference to undefined property installInfo.installs TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_whitelist2.js | Install should have been triggered by the right window TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_whitelist2.js | Install should have been triggered by the right uri up+0x000000000000000F (f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c, line 403) kernel32!BaseThreadInitThunk+0x0000000000000012 ntdll!RtlInitializeExceptionChain+0x0000000000000063 ntdll!RtlInitializeExceptionChain+0x0000000000000036 JavaScript strict warning: chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/head.js, line 211: reference to undefined property installInfo.installs TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_whitelist2.js | Should only see cancelations for started installs *** LOG addons.xpi: Cancelling download of http://example.org/browser/toolkit/mozapps/extensions/test/xpinstall/unsigned.xpi TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/browser_auth2.js | Console message: [JavaScript Warning: "reference to undefined property installInfo.installs" {file: "chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/xpinstall/head.js" line: 303}]
Summary: xpinstall/head.js, line 321: reference to undefined property installInfo.installs → xpinstall/head.js, lines 221, 303 and 321: reference to undefined property installInfo.installs
From a single run there are 356 lines of output on a Windows debug build with 'reference to undefined property installInfo.installs'
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: