Closed Bug 992112 Opened 11 years ago Closed 9 years ago

Critical framework error in shutdownApplication() when calling Services.obs.notifyObservers

Categories

(Testing Graveyard :: Mozmill, defect)

x86_64
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: whimboo, Unassigned)

References

Details

For some of our update tests I have seen a critical failure in frame.js when we tried to call: Services.obs.notifyObservers(cancelQuit, "quit-application-requested", null); Not sure what exactly this is about. We should investigate if it happens more often. Here the logging information: 00:02:17.223 TEST-START | test1.js | setupModule 00:02:17.402 TEST-START | test1.js | teardownModule 00:02:17.402 TEST-END | test1.js | finished in 222ms 00:02:33.467 CRITICAL | Framework Failure | { 00:02:33.467 "message": "[JavaScript Error: \"[Exception... \"'[object Object]' when calling method: [nsIObserver::observe]\" nsresult: \"0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)\" location: \"JS frame :: resource://mozmill/modules/frame.js :: shutdownApplication :: line 65\" data: no]\" {file: \"resource://mozmill/modules/frame.js\" line: 65}]" 00:02:33.467 } https://github.com/mozilla/mozmill/blob/hotfix-2.0/mozmill/mozmill/extension/resource/modules/frame.js#L65
Blocks: 1035187
We are not going back to use Mozmill for our UI testing of Firefox and this failure hasn't even be seen for a long time.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.