Closed
Bug 856541
Opened 12 years ago
Closed 12 years ago
Failure "Disconnect Error: Application unexpectedly closed" in testEnableCookies.j, testDisableCookies.js and testRemoveAllCookies.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox22 affected, firefox23 affected, firefox24 affected, firefox25 affected, firefox-esr17 affected)
People
(Reporter: andrei, Assigned: cosmin-malutan)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Attachments
(2 files)
Only 1 failure on Windows 7, Nightly, en-US:
http://mozmill-ci.blargon7.com/#/functional/report/25ad365ca7bcf4905e9b700b4f59d4de
Reporter | ||
Updated•12 years ago
|
status-firefox22:
--- → affected
Updated•12 years ago
|
Priority: -- → P3
Comment 1•12 years ago
|
||
One again today and also in testDisableCookie.js, both on Aurora, Windows 8, de and en-US locales:
http://mozmill-ci.blargon7.com/#/functional/report/8ec48e7ab0431a61b624e36d31c01224
http://mozmill-ci.blargon7.com/#/functional/report/8ec48e7ab0431a61b624e36d31bea3b1
The one in Andrei's report from above is also Windows 8, not 7.
I see one more failure on April 10th, which was on Linux:
http://mozmill-ci.blargon7.com/#/functional/report/cb9e33213cf3d2f37d7b0f8dcc8b4ec8
OS: Windows 7 → All
Hardware: x86 → All
Summary: Failure "Disconnect Error: Application unexpectedly closed" in /testPreferences/testEnableCookies.js → Failure "Disconnect Error: Application unexpectedly closed" in /testPreferences/testEnableCookies.js and testDisableCookies.js
Whiteboard: [mozmill-test-failure]
Comment 2•12 years ago
|
||
Happened on Aurora and Windows 8 x86 today:
http://mozmill-ci.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa0679aaa8
Comment 3•12 years ago
|
||
Happened again on Aurora and Windows 8:
http://mozmill-ci.blargon7.com/#/functional/report/452ec32f8deec0960aea87aa06b8361e
Comment 4•12 years ago
|
||
Happened again on Windows NT 6.2.9200 (x86_64) with Firefox 22.0a2 fr
View the build in Jenkins:
http://mm-ci-master.qa.scl3.mozilla.com:8080/job/mozilla-aurora_functional/3359/
View the results in the Mozmill Dashboard:
http://mozmill-ci.blargon7.com/#/functional/report/ea82256a8ae9808d91b7e8145e23e04b
http://mozmill-ci.blargon7.com/#/functional/report/ea82256a8ae9808d91b7e8145e245eed
Comment 5•12 years ago
|
||
Happened again on Windows 8 x64 with Aurora 23.0a2:
http://mozmill-ci.blargon7.com/#/functional/report/14f8bc4e22e61353662cded4c2e2b3a4
status-firefox23:
--- → affected
Comment 6•12 years ago
|
||
Happened on Nightly IT on Windows 8:
http://mozmill-ci.blargon7.com/#/functional/report/90a0b225333a4e0c868fcb2b448d493c
status-firefox24:
--- → affected
Comment 7•12 years ago
|
||
Happened with Nightly DE on Windows 8 in 5/26:
http://mozmill-ci.blargon7.com/#/functional/report/90a0b225333a4e0c868fcb2b44d46d04
Comment 8•12 years ago
|
||
Happened on ESR17 with Windows 8 x64:
http://mozmill-ci.blargon7.com/#/functional/report/f2d3b6136b11cb7b6708636cff4b224e
status-firefox-esr17:
--- → affected
Comment 9•12 years ago
|
||
Happened on Windows NT 6.2.9200 (x86) with Firefox 25.0a1 it:
http://mozmill-ci.blargon7.com/#/functional/report/a1b02004612785c13cf7c6bf1e8bd2c2
Updated•12 years ago
|
status-firefox25:
--- → affected
Comment 10•12 years ago
|
||
Firefox 23.0 (23.0, ja, 20130718163513) on Windows NT 6.2.9200 (x86_64):
http://mozmill-release.blargon7.com/#/functional/report/180cf2548ef2865af3ae441d61206560
Comment 11•12 years ago
|
||
This seems to be mostly happening on Windows 8. Mario, could you spot-check the affected locales so we may find out what's happening here? Thanks.
Severity: normal → critical
Flags: needinfo?(mario.garbi)
Comment 12•12 years ago
|
||
This happened mostly on Win8 indeed, only once on Linux. We had failures on Aurora and Nightly mostly and once on ESR17 with all locales (de, fr, it, en-US).
We only had one failure this year with ondemand tests on Beta 23 JA.
I will test a couple more exotic locales locally and see if I can reproduce the issue on other locales.
Flags: needinfo?(mario.garbi)
Comment 13•12 years ago
|
||
After running functional tests on Win8 X86 with a couple of exotic locales we couldn't reproduce it even once.
http://mozmill-crowd.blargon7.com/#/functional/reports?branch=All&platform=Windows%20NT&from=2013-07-23&to=2013-07-23
Updated•12 years ago
|
Assignee: nobody → mario.garbi
Status: NEW → ASSIGNED
Reporter | ||
Comment 15•12 years ago
|
||
Updated failure links with new ci dashboard url:
http://mozmill-daily.blargon7.com/#/functional/failure?branch=All&platform=All&from=2013-07-01&test=%2FtestPreferences%2FtestRemoveAllCookies.js&func=testRemoveAllCookies
http://mozmill-daily.blargon7.com/#/functional/failure?branch=All&platform=All&from=2013-07-01&test=%2FtestPreferences%2FtestEnableCookies.js&func=testEnableCookies
http://mozmill-daily.blargon7.com/#/functional/failure?branch=All&platform=All&from=2013-07-01&test=%2FtestPreferences%2FtestDisableCookies.js&func=testDisableCookies
I only see Windows 8 here.
Might be related to the Windows 8 overlay issue, see bug 900860
Latest failure I see is from 7th August (before I updated all Win8 machines).
To be sure, as this is already assigned to Mario, please track this, if no new failures in 2 weeks please close.
Reporter | ||
Updated•12 years ago
|
Summary: Failure "Disconnect Error: Application unexpectedly closed" in /testPreferences/testEnableCookies.js and testDisableCookies.js → Failure "Disconnect Error: Application unexpectedly closed" in testEnableCookies.j, testDisableCookies.js and testRemoveAllCookies.js
Comment 16•12 years ago
|
||
Latest failure was from yesterday 18.08.2013 so it doesn't seem to be fixed. I will look into it on the failing machine as soon as possible.
Comment 17•12 years ago
|
||
We had another failure on Windows NT 6.2.9200 (x86_64) with Firefox 24.0 (24.0, pt-BR, 20130902131354). This happened for testRemoveAllCookies.js which is failing more than the others with Disconnect Error.
http://mozmill-release.blargon7.com/#/functional/report/3c3cd991de01b704f3f65783a1cb7fdd
Comment 18•12 years ago
|
||
We had another couple of failures in testDisableCookies.js . The Jenkins console log isn't showing much but I will upload it in case we need it in the future.
Comment 20•12 years ago
|
||
This happens more often now. It's not that often for a P1 but we should get it investigated and reproduced.
Priority: P3 → P1
Comment 21•12 years ago
|
||
This happened yesterday with a beta candidate build. So please make that a priority to get fixed. Thanks.
Reporter | ||
Updated•12 years ago
|
Comment 22•12 years ago
|
||
I can reproduce this on the machine win8-32-1 with the functional testrun. In case of the cookie tests, our test opens the preferences dialog but when we click on 'Show Cookies' Firefox freezes and does not respond. I will take this and try to nail it down as fast as possible.
Assignee: mario.garbi → hskupin
Comment 23•12 years ago
|
||
Cosmin, given that you watched my testing, could you take this over? It looks like we are getting a lot of freezes now. Given that I have to finalize Mozmill 2.0, it would be great if you can find a minimized testcase or the underlying cause here. Thanks.
Assignee: hskupin → cosmin.malutan
Assignee | ||
Comment 24•12 years ago
|
||
I investigated those disconnect errors today but I couldn't reduce the testcase, what I found out is that the CPU is loaded at 100%, and the antimalware program takes the most of resources, I will investigate this further but I think that we should allow more cores for windows 8 machines or to disable the antimalware.
Comment 25•12 years ago
|
||
Well, none of the processes cause a cpu load of nearly 100%. How long caused the antimalware tool that higher cpu load? Can you check next time what it does? Would be good to know to make it reproducible.
Comment 26•12 years ago
|
||
Cosmin, is that bug still reproducible? If not I tend to say we close it as fixed by bug 919676.
Assignee | ||
Comment 27•12 years ago
|
||
The failure did't reproduced since we disabled windows defender, so I close this bug as fixed.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•