Closed
Bug 614868
Opened 14 years ago
Closed 14 years ago
Fix the plugin blocklisting test to handle a new window which is opened when we update our blocklist
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla2.0b8
People
(Reporter: ehsan.akhgari, Assigned: mossop)
References
Details
Attachments
(1 file)
1.65 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
After this changeset <http://hg.mozilla.org/mozilla-central/rev/25a981d7de7d> landed, test_bug430120.js <http://hg.mozilla.org/mozilla-central/annotate/765087b28561/toolkit/mozapps/extensions/test/xpcshell/test_bug430120.js> started to fail like this: <http://tinderbox.mozilla.org/showlog.cgi?tree=Firefox&errorparser=unittest&logfile=1290716791.1290718885.3500.gz&buildtime=1290716791&buildname=WINNT%205.2%20mozilla-central%20debug%20test%20xpcshell&fulltext=1#err0> TEST-INFO | e:\builds\moz2_slave\mozilla-central-win32-debug-unittest-xpcshell\build\xpcshell\tests\toolkit\mozapps\extensions\test\xpcshell\test_bug430120.js | running test ... TEST-UNEXPECTED-FAIL | e:\builds\moz2_slave\mozilla-central-win32-debug-unittest-xpcshell\build\xpcshell\tests\toolkit\mozapps\extensions\test\xpcshell\test_bug430120.js | test failed (with xpcshell return code: -2147483645), see following log: >>>>>>> ### XPCOM_MEM_LEAK_LOG defined -- logging leaks to c:\docume~1\cltbld\locals~1\temp\tmpycyspn\runxpcshelltests_leaks.log pldhash: for the table at address 0543E558, the given entrySize of 48 probably favors chaining over double hashing. TEST-INFO | (xpcshell/head.js) | test 1 pending\nTEST-PASS | e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-xpcshell/build/xpcshell/tests/toolkit/mozapps/extensions/test/xpcshell/test_bug430120.js | [run_test : 150] true == true\nTEST-INFO | (xpcshell/head.js) | test 2 pending\nnsNativeModuleLoader::LoadModule("e:\builds\moz2_slave\mozilla-central-win32-debug-unittest-xpcshell\build\firefox\components\xpcomsample.dll") - load FAILED, rv: 80520012, error: <unknown; can't get error from NSPR> *** Blocklist::_loadBlocklistFromFile: blocklist is disabled *** Blocklist state for Test Plug-in changed from -1 to 0 *** Blocklist state for Windows Presentation Foundation changed from -1 to 0 *** Blocklist state for Java Deployment Toolkit 6.0.140.8 changed from -1 to 0 *** Blocklist state for Java(TM) Platform SE 6 U14 changed from -1 to 0 *** Blocklist state for Test Plug-in changed from -1 to 0 *** Blocklist state for Windows Presentation Foundation changed from -1 to 0 *** Blocklist state for Java Deployment Toolkit 6.0.140.8 changed from -1 to 1 *** Blocklist state for Java(TM) Platform SE 6 U14 changed from -1 to 0 ###!!! ASSERTION: attempted to open a new window with no WindowCreator: 'mWindowCreator', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/embedding/components/windowwatcher/src/nsWindowWatcher.cpp, line 687 nsStringStats => mAllocCount: 2787 => mReallocCount: 61 => mFreeCount: 708 -- LEAKED 2079 !!! => mShareCount: 7511 => mAdoptCount: 128 => mAdoptFreeCount: 126 -- LEAKED 2 !!! xul!DumpJSValue+0x0000000000169DC5 xul!NS_InvokeByIndex_P+0x0000000000000027 xul!DumpJSValue+0x00000000000478E8 xul!DumpJSValue+0x00000000000459BF xul!DumpJSValue+0x000000000004574D xul!DumpJSValue+0x000000000002A53C mozjs!JS_AlreadyHasOwnProperty+0x00000000000CF54C mozjs!JS_AlreadyHasOwnProperty+0x00000000000E0D2A mozjs!JS_AlreadyHasOwnProperty+0x00000000000CEC54 mozjs!JS_AlreadyHasOwnProperty+0x00000000000CF0BF mozjs!JS_AlreadyHasOwnProperty+0x00000000000A5EEB mozjs!JS_AlreadyHasOwnProperty+0x00000000000CF54C mozjs!JS_AlreadyHasOwnProperty+0x00000000000E0D2A mozjs!JS_AlreadyHasOwnProperty+0x00000000000CEC54 mozjs!JS_AlreadyHasOwnProperty+0x00000000000CF0BF mozjs!JS_AlreadyHasOwnProperty+0x00000000000D00AB mozjs!JS_AlreadyHasOwnProperty+0x0000000000033718 mozjs!JS_AlreadyHasOwnProperty+0x0000000000033B6C xul!DumpJSValue+0x00000000000FACCB xul!DumpJSValue+0x00000000000F54A3 xul!NS_InvokeByIndex_P+0x0000000000000556 xul!NS_InvokeByIndex_P+0x0000000000000226 xul!gfxSize::operator=+0x000000000007C1B6 xul!gfxSize::operator=+0x0000000000087C02 xul!gfxSize::operator=+0x0000000000087596 xul!gfxSize::operator=+0x00000000000861AE xul!gfxSize::operator=+0x00000000000796F9 xul!gfxSize::operator=+0x000000000007F940 xul!NS_InvokeByIndex_P+0x0000000000000027 xul!DumpJSValue+0x00000000000478E8 xul!DumpJSValue+0x00000000000459BF xul!DumpJSValue+0x000000000004574D xul!DumpJSValue+0x000000000002A53C mozjs!JS_AlreadyHasOwnProperty+0x00000000000CF54C mozjs!JS_AlreadyHasOwnProperty+0x00000000000E0D2A mozjs!JS_AlreadyHasOwnProperty+0x00000000000CEC54 mozjs!JS_AlreadyHasOwnProperty+0x00000000000D07DD mozjs!JS_AlreadyHasOwnProperty+0x00000000000332A8 mozjs!JS_AlreadyHasOwnProperty+0x0000000000033433 0x0000000000405C86 0x0000000000404A5D 0x0000000000413066 0x0000000000412EBD kernel32!ProcessIdToSessionId+0x0000000000000209 ###!!! ASSERTION: attempted to open a new window with no WindowCreator: 'mWindowCreator', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/embedding/components/windowwatcher/src/nsWindowWatcher.cpp, line 687 <<<<<<< I think this is happening because we're trying to open a new window here: <http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/nsBlocklistService.js#908>. Why this only failed on Win debug is a mystery to me. This needs to be fixed before we can land any blocklist.xml updates on mozilla-central, I think.
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Assignee | ||
Comment 1•14 years ago
|
||
This means that the tinderboxen have a blocklisted plugin installed on them (looks like Java Deployment Toolkit).
Assignee: nobody → dtownsend
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > This means that the tinderboxen have a blocklisted plugin installed on them > (looks like Java Deployment Toolkit). Heh, awesome! Then I guess we should move this to IT to ask them to uninstall it, right?
Assignee | ||
Comment 3•14 years ago
|
||
Well it'd certainly be worth looking at what in on those machines and why it was blocklisted, but we can also make the test more resilient anyway. I've just pushed something to try that would probably fix the problem.
Reporter | ||
Comment 4•14 years ago
|
||
(In reply to comment #3) > Well it'd certainly be worth looking at what in on those machines and why it > was blocklisted, but we can also make the test more resilient anyway. I've just > pushed something to try that would probably fix the problem. OK, yes, that sounds reasonable. Thanks!
http://www.mozilla.com/en-US/blocklist/: Java Deployment Toolkit, versions 6.0.200.0 and older. Reason: security vulnerabilities (see bug 558584).
Assignee | ||
Comment 6•14 years ago
|
||
(In reply to comment #5) > http://www.mozilla.com/en-US/blocklist/: > > Java Deployment Toolkit, versions 6.0.200.0 and older. Reason: security > vulnerabilities (see bug 558584). A skim of the issue suggests that since the tinderbox machines aren't being used to browse random websites there is probably not much urgency in updating them immediately.
Assignee | ||
Comment 7•14 years ago
|
||
This writes an empty blocklist to the test profile so the app-provided blocklist is ignored. This seems better than ignoring any open window as it ensures a stable testing environment.
Attachment #494552 -
Flags: review?(robert.bugzilla)
Assignee | ||
Updated•14 years ago
|
Whiteboard: [has patch][needs review rs]
Updated•14 years ago
|
Attachment #494552 -
Flags: review?(robert.bugzilla) → review+
Updated•14 years ago
|
Whiteboard: [has patch][needs review rs] → [has patch]
Assignee | ||
Comment 8•14 years ago
|
||
Landed: http://hg.mozilla.org/mozilla-central/rev/b8388f11a366
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Flags: in-litmus-
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b8
Assignee | ||
Updated•14 years ago
|
Whiteboard: [has patch]
Comment 9•14 years ago
|
||
Mossop: does this need backporting to 1.9.2/1.9.1?
Assignee | ||
Comment 10•14 years ago
|
||
Looks like yes, I'll get on that today
Assignee | ||
Comment 11•14 years ago
|
||
Fixed on the branches: http://hg.mozilla.org/releases/mozilla-1.9.2/rev/53170e1be1bd http://hg.mozilla.org/releases/mozilla-1.9.1/rev/f66accc3afef
status1.9.1:
--- → .17-fixed
status1.9.2:
--- → .14-fixed
Assignee | ||
Updated•14 years ago
|
blocking2.0: ? → final+
Comment 12•14 years ago
|
||
No more test failures since the landing of the patch. Marking as verified fixed.
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
You need to log in
before you can comment on or make changes to this bug.
Description
•