User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20130805 Firefox/24.0 (Nightly/Aurora) Build ID: 20130805004006 Steps to reproduce: When running "make SOLO_TEST=content-tabs/test-plugin-crashing.js mozmill-one" (but also other tests, I get this: Failed to load file:///home/jens/devel/releases-comm-central/mailnews/base/prefs/content/AccountManager.js

This is printed in XULDocument.cpp:3488.

The error code is: NS_BINDING_ABORTED (0x804B0002) The asynchronous request failed because it was aborted by some user action.

Yes, I also often see this (I think also in normal Daily startups) but have never found the cause. And it is not known if it causes any problem. But yes, it is ugly because the file does exist.

(In reply to :aceman from comment #3) > But yes, it is ugly because the file does exist. As I wrote: The reason the load fails is not "file not found", but "The asynchronous request failed because it was aborted by some user action."

Hi, I also observe the errorr message sin my session log of running "make mozmill" of DEBUG BUILD of TB. Most of the "Failed to load file: ... AccountManager.js" error messages during "make mozmill" run appear in the following sequence of error/warning messages. (Note that I am running the automated test sequence. So in that sense, I highly doubt I am doing much user interaction although I do understand that the test harness try to emulate key events and other UI-actions.) Note the undefined property warning before the load failure, and the mScriptGlobalObject warnings after the load failure message and before 0x80004005 error code is printed. [...] JavaScript strict warning: chrome://messenger/content/tabmail.xml, line 352: reference to undefined property aTabType.panelId ++DOMWINDOW == 26 (0xb974720) [serial = 26] [outer = 0x9e9ca18] Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js ++DOMWINDOW == 27 (0xb98dfd8) [serial = 27] [outer = 0x9e9ca18] WARNING: NS_ENSURE_TRUE(mScriptGlobalObject) failed: file /REF-COMM-CENTRAL/comm-central/mozilla/content/xul/document/src/XULDocument.cpp, line 3665 WARNING: NS_ENSURE_TRUE(mScriptGlobalObject) failed: file /REF-COMM-CENTRAL/comm-central/mozilla/content/xul/document/src/XULDocument.cpp, line 3665 WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file /REF-COMM-CENTRAL/comm-central/mailnews/base/src/nsMsgAccountManager.cpp, line 2379 During the whole "make mozmill" run, the error appears in one case like the following with a javascript error preceding it.: [...] JavaScript strict warning: chrome://messenger/content/tabmail.xml, line 352: reference to undefined property aTabType.panelId ++DOMWINDOW == 26 (0xc557e60) [serial = 26] [outer = 0xaf12e30] ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "'[JavaScript Error: "document.getElementById(...) is null" {file: "chrome://messenger/content/chat/imStatusSelector.js" line: 36}]' when calling method: [nsIObserver::observe]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: resource:///modules/chatHandler.jsm :: ChatCore.init/<.onPromptStart :: line 74" data: yes] ************************************************************ Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js ++DOMWINDOW == 27 (0xc5aa290) [serial = 27] [outer = 0xaf12e30] WARNING: NS_ENSURE_TRUE(mScriptGlobalObject) failed: file /REF-COMM-CENTRAL/comm-central/mozilla/content/xul/document/src/XULDocument.cpp, line 3665 WARNING: NS_ENSURE_TRUE(mScriptGlobalObject) failed: file /REF-COMM-CENTRAL/comm-central/mozilla/content/xul/document/src/XULDocument.cpp, line 3665 WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file /REF-COMM-CENTRAL/comm-central/mailnews/base/src/nsMsgAccountManager.cpp, line 2379 --DOCSHELL 0xaf127c8 == 10 [id = 3] But this particular case is followed by the error messages/warnings. So I suspect some thread-races. --DOCSHELL 0xaf127c8 == 10 [id = 3] --DOCSHELL 0xb561318 == 9 [id = 9] --DOCSHELL 0xb0378e0 == 8 [id = 6] --DOCSHELL 0xa718958 == 7 [id = 1] WARNING: An event was posted to a thread that will never run it (rejected): file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/threads/nsThread.cpp, line 353 WARNING: unable to post continuation event: file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/io/nsStreamUtils.cpp, line 438 WARNING: An event was posted to a thread that will never run it (rejected): file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/threads/nsThread.cpp, line 353 WARNING: unable to post continuation event: file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/io/nsStreamUtils.cpp, line 438 --DOCSHELL 0xb5431d8 == 6 [id = 7] --DOCSHELL 0xb560470 == 5 [id = 8] --DOCSHELL 0xb5623a8 == 4 [id = 10] --DOCSHELL 0xb56fb70 == 3 [id = 11] --DOCSHELL 0xb027240 == 2 [id = 4] --DOCSHELL 0xa88bf78 == 1 [id = 2] --DOMWINDOW == 26 (0xbfdfcc0) [serial = 20] [outer = 0xb037ed0] [url = about:blank] --DOMWINDOW == 25 (0xbff7c00) [serial = 23] [outer = 0xb561998] [url = about:blank] --DOMWINDOW == 24 (0xa207aa8) [serial = 2] [outer = 0xa72b838] [url = about:blank] WARNING: nsExceptionService ignoring thread destruction after shutdown: file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/base/nsExceptionService.cpp, line 168 --DOMWINDOW == 23 (0xbfbc750) [serial = 19] [outer = 0xb028ea8] [url = about:blank] --DOMWINDOW == 22 (0xb516fd8) [serial = 21] [outer = 0xb5438e8] [url = about:blank] --DOMWINDOW == 21 (0xbff0ef8) [serial = 22] [outer = 0xb560a60] [url = about:blank] --DOMWINDOW == 20 (0xc000c18) [serial = 24] [outer = 0xb562a08] [url = about:blank] --DOMWINDOW == 19 (0xc009268) [serial = 25] [outer = 0xb570240] [url = about:blank] --DOMWINDOW == 18 (0xbe82668) [serial = 15] [outer = 0xb562a08] [url = about:blank] --DOMWINDOW == 17 (0xbed1800) [serial = 16] [outer = 0xb5438e8] [url = about:blank] --DOMWINDOW == 16 (0xb561998) [serial = 12] [outer = (nil)] [url = about:blank] --DOMWINDOW == 15 (0xb037ed0) [serial = 9] [outer = (nil)] [url = about:blank] --DOMWINDOW == 14 (0xb5438e8) [serial = 10] [outer = (nil)] [url = about:blank] --DOMWINDOW == 13 (0xb560a60) [serial = 11] [outer = (nil)] [url = about:blank] --DOMWINDOW == 12 (0xb562a08) [serial = 13] [outer = (nil)] [url = about:blank] --DOMWINDOW == 11 (0xb570240) [serial = 14] [outer = (nil)] [url = about:blank] --DOMWINDOW == 10 (0xb028ea8) [serial = 8] [outer = (nil)] [url = about:blank] WARNING: unable to Flush() dirty datasource during XPCOM shutdown: file /REF-COMM-CENTRAL/comm-central/mozilla/rdf/base/src/nsRDFXMLDataSource.cpp, line 747 --DOMWINDOW == 9 (0xa8ec688) [serial = 5] [outer = 0xa72b838] [url = resource://gre-resources/hiddenWindow.html] --DOMWINDOW == 8 (0xa72b838) [serial = 1] [outer = (nil)] [url = resource://gre-resources/hiddenWindow.html] --DOMWINDOW == 7 (0xbb43648) [serial = 17] [outer = (nil)] [url = about:blank] --DOMWINDOW == 6 (0xc557e60) [serial = 26] [outer = (nil)] [url = chrome://messenger/content/msgAccountCentral.xul] --DOMWINDOW == 5 (0xc5aa290) [serial = 27] [outer = (nil)] [url = chrome://messenger/content/msgAccountCentral.xul] --DOMWINDOW == 4 (0xbc8a8e8) [serial = 18] [outer = (nil)] [url = chrome://messenger/content/multimessageview.xhtml] --DOMWINDOW == 3 (0xb027878) [serial = 7] [outer = (nil)] [url = chrome://messenger/content/multimessageview.xhtml] --DOMWINDOW == 2 (0xaf12e30) [serial = 6] [outer = (nil)] [url = chrome://messenger/content/msgAccountCentral.xul] WARNING: not an nsIRDFRemoteDataSource: 'remote != nullptr', file /REF-COMM-CENTRAL/comm-central/mozilla/rdf/datasource/src/nsLocalStore.cpp, line 279 WARNING: not an nsIRDFRemoteDataSource: 'remote != nullptr', file /REF-COMM-CENTRAL/comm-central/mozilla/rdf/datasource/src/nsLocalStore.cpp, line 279 WARNING: Leaking the RDF Service.: file /REF-COMM-CENTRAL/comm-central/mozilla/rdf/build/nsRDFModule.cpp, line 165 WARNING: YOU ARE LEAKING THE WORLD (at least one JSRuntime and everything alive inside it, that is) AT JS_ShutDown TIME. FIX THIS! ###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt == 0', file /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/build/nsXPComInit.cpp, line 789 [...] Given the one case where thread-race is implicated, and I get the error messages during automated test run, I suspect that TB has an inherent thread-race issue that somehow breaks loading of AccountManager.js somewhere. Hope this helps. I am sorry that I have not reported this strange failure to bugzilla. There are simply TOO MANY pressing error/warning messages from the "make mozmill" run of DEBUG BUILD of TB :-( I am glad that this strange message is noticed and this bugzilla entry is entered by bugzilla. TIA

> JavaScript strict warning: chrome://messenger/content/tabmail.xml, line 352: reference to undefined property aTabType.panelId ++DOMWINDOW == 26 (0xb974720) [serial = 26] [outer = 0x9e9ca18] > Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js Interesting. Bug 903636 tries to solve the "reference to undefined property aTabType.panelId". In that bug we identified an accountProvisionerTabType object that possibly causes this warning. That one quite probably is used from AccountManager. What if that JS warning aborts the load of AccountManager.js in this case but it does not fail when called later in TB run.

(In reply to :aceman from comment #6) > In that bug we identified an accountProvisionerTabType > object that possibly causes this warning. It could also be any of the tab types with panelPerTab, couldn't it?

Sure, but this one strikes me as possibly being called from AM.

(In reply to :aceman from comment #6) > > JavaScript strict warning: chrome://messenger/content/tabmail.xml, line 352: reference to undefined property aTabType.panelId > ++DOMWINDOW == 26 (0xb974720) [serial = 26] [outer = 0x9e9ca18] > > > Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js > > Interesting. Bug 903636 tries to solve the "reference to undefined property > aTabType.panelId". In that bug we identified an accountProvisionerTabType > object that possibly causes this warning. That one quite probably is used > from AccountManager. What if that JS warning aborts the load of > AccountManager.js in this case but it does not fail when called later in TB > run. Gee, I have somehow failed to follow up on this thread. Today I noticed this failure to load which goes all the way back to my oldest log kept on the current PC. We still have many subtle issues to clean up for C-C TB. I added 903636 in the See also field.

BTW, just before this message appears, often times, I see the following errors. (Again, these have been is printed for a long time.) Failed to open errors In th list below, the first # is Frequency of occurences: the process/task ID [nnn] should be ignored. The first three errors look very similar, but they differ in the base components. The first one's base ends with "selected-start.svg", the second one with "selected-end.svg", and the third one ends with "closeTab.svg" The first two errors are often seen several lines before "Failed to load" error message. 36 [1389] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/selected-start.svg" URL "resource://gre/res/dtd/svg11.dtd": file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 703 36 [1389] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/selected-end.svg" URL "resource://gre/res/dtd/svg11.dtd": file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 703 11 [2535] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/closeTab.svg" URL "resource://gre/res/dtd/svg11.dtd": file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 703 1 [3061] WARNING: Failed to open external DTD: publicId "" systemId "resource:///res/dtd/xhtml11.dtd" base "moz-nullprincipal:{b4c5d127-8f10-4eaf-bbda-2d74e3aebf35}" URL "resource://gre/res/dtd/xhtml11.dtd": file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 703 This is printed in the following: http://mxr.mozilla.org/comm-central/source/mozilla/parser/htmlparser/nsExpatDriver.cpp#694 Maybe it is due to the same >NS_BINDING_ABORTED (0x804B0002) > The asynchronous request failed because it was aborted by some user action I should find out why this fails, but for that matter I wonder WHY TB needs to load this DTD from remote site. W3C specifically wants tools to load a local copy instead of accessing these URI (!) remotely the last time I checked a few years ago about this strange message. Or is TB failing to load these dtd from a local copy which is missing or something? f. Failed to load errors. The first # is Frequency of occurences. 28 Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js 1 Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/am-serverwithnoidentities.js TIA

How is bug 903636 related?

(In reply to :aceman from comment #11) > How is bug 903636 related? Please see comment 6: --- begin excerpt --- > Failed to load file:///REF-COMM-CENTRAL/comm-central/mailnews/base/prefs/content/AccountManager.js Interesting. Bug 903636 tries to solve the "reference to undefined property aTabType.panelId". In that bug we identified an accountProvisionerTabType object that possibly causes this warning. That one quite probably is used from AccountManager. What if that JS warning aborts the load of AccountManager.js in this case but it does not fail when called later in TB run. --- end excerpt Well, guess who wrote the comment about two years ago: it was from you :-) TIA

(In reply to ISHIKAWA, Chiaki from comment #10) > BTW, just before this message appears, often times, I see the following > errors. > (Again, these have been is printed for a long time.) > > Failed to open errors > I found out that they were failed to open because >NS_ERROR_FILE_NOT_FOUND (0x80520012) > An attempt was made to access a file that does not exist. Use nsIFile.exists() to >check if the file exists beforehand. Please note the error code that is printed in the error message (I added this). So it looks that "resource://gre/res/dtd/svg11.dtd" "resource://gre/res/dtd/xhtml11.dtd" are not readable or something. I have no idea. Maybe I am running a binary without installing it. Or an oversight of packaging. Maybe I should file a bug about this. ======================================== Failed to open modulo process id ======================================== 36 [23048] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COerror code = 0x80520012: file /REF-COMM-CENTRAL/comm-centrMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/selected-start.svg" URL "resource://gre/res/dtd/svg11.dtd"al/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 709 36 [23048] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/selected-end.svg" URL "resource://gre/res/dtd/svg11.dtd"error code = 0x80520012: file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 709 11 [23630] WARNING: Failed to open external DTD: publicId "-//W3C//DTD SVG 1.1//EN" systemId "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" base "file:///REF-COMM-CENTRAL/comm-central/mail/themes/linux/mail/tabs/closeTab.svg" URL "resource://gre/res/dtd/svg11.dtd"error code = 0x80520012: file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 709 1 [23976] WARNING: Failed to open external DTD: publicId "" systemId "resource:///res/dtd/xhtml11.dtd" base "moz-nullprincipal:{8bea6e6d-772b-4abb-b358-818dbb34766b}" URL "resource://gre/res/dtd/xhtml11.dtd"error code = 0x80520012: file /REF-COMM-CENTRAL/comm-central/mozilla/parser/htmlparser/nsExpatDriver.cpp, line 709 At least, now I am about to solve an issue that has remained a mystery for a few years.