I have seen discussions going on about
the dependency issues of modules during shutdown processes of mozilla
software.
Just in case, nobody knows, here are
quotes from session log of running debug build of TB
using "make mozmill" test harness. (Is Debug build of TB produced and tested
by mozilla officially? This is a local build from comm-central tree.
Looking at the log, I think it is very worthwhile to do so.)
These are noticed simply by looking for "shutdown" in the log, and
duplicates are eliminated. There are MANY of them.
The messages are not quite reassuring and I wonder if a few crashes of
thunderbird (the production version) under linux I noticed in the last few
months
can be related to the issues noted below.
TIA
---
WARNING: nsExceptionService ignoring thread destruction after shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/base/nsExceptionService.cpp,
line 167
WARNING: unable to Flush() diry datasource during XPCOM shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/base/src/nsRDFXMLDataSource.cpp,
line 745
---
###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt ==
0', file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/build/nsXPComInit.cpp, line
670
---
WARNING: nsExceptionService ignoring thread destruction after shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/base/nsExceptionService.cpp,
line 167
WARNING: unable to Flush() diry datasource during XPCOM shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/base/src/nsRDFXMLDataSource.cpp,
line 745
---
WARNING: nsExceptionService ignoring thread destruction after shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/base/nsExceptionService.cpp,
line 167
WARNING: unable to Flush() diry datasource during XPCOM shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/base/src/nsRDFXMLDataSource.cpp,
line 745
WARNING: not an nsIRDFRemoteDataSource: 'remote != nullptr', file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/datasource/src/nsLocalStore.cpp,
line 279
--DOMWINDOW == 7 (0x3270e88) [serial = 7] [outer = (nil)] [url =
chrome://messenger/content/multimessageview.xhtml]
---
WARNING: nsExceptionService ignoring thread destruction after shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/base/nsExceptionService.cpp,
line 167
************************************************************
* Call to xpconnect wrapped JSObject produced this error: *
[Exception... "'[JavaScript Error: "XPIProvider.installLocationsByName is null"
{file:
"resource://gre/modules/XPIProvider.jsm ->
resource://gre/modules/XPIProviderUtils.js" line: 1275}]' when calling
method: [mozIStorageStatementCallback::handleResult]" nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "native frame ::
<unknown filename> :: <TOP_LEVEL> :: line 0"
data: yes]
************************************************************
WARNING: unable to Flush() diry datasource during XPCOM shutdown: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/base/src/nsRDFXMLDataSource.cpp,
line 745
---
In a long series:
Actually what bothers me very much is "some msg dbs left
open" message, and I noticed this precedes or related to
"held past XPCOM shutdown" warning. [I wonder what happens when a crash occurs.
WIll my
messages be intact?]
WARNING: Leaking the RDF Service.: file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/rdf/build/nsRDFModule.cpp, line 165
WARNING: Fonts still alive while shutting down gfxFontCache: 'mFonts.Count() ==
0', file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/gfx/thebes/gfxFont.cpp, line 1270
Assertion failed at
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/gfx/cairo/cairo/src/cairo-hash.c:196:
hash_table->live_entries == 0
WARNING: some msg dbs left open: '!m_dbCache->Length()', file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mailnews/db/msgdb/src/nsMsgDatabase.cpp,
line 915
db left open
/home/ishikawa/TB-NEW/TB-3HG/objdir-tb3/mozilla/_tests/mozmill/mozmillprofile/Mail/Local
Folders/AttachmentA.msf
db left open
/home/ishikawa/TB-NEW/TB-3HG/objdir-tb3/mozilla/_tests/mozmill/mozmillprofile/Mail/Local
Folders/AttachmentMenusA.msf
###!!! ASSERTION: Component Manager being held past XPCOM shutdown.: 'cnt ==
0', file
/home/ishikawa/TB-NEW/TB-3HG/new-src/mozilla/xpcom/build/nsXPComInit.cpp, line
670
The situation is similar both in 32-bit and 64-bit builds.
Since they warnings are very general and I could not focus in particular
problem, I
have not touched the code anyway. But just thought it would be a good idea to
voice
the comm-central TB suffers from these issues. just in case nobody else
is aware of these TB problems.
(I am working on much smaller very focused issues that I found in the session
log for now.)
I want my mail client to be rock solid, but TB as of now is not :-(
TIA
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
