37465 - Assertions running news://host/article, news://host/group, or doing new message when you have zero accounts.

Status: RESOLVED FIXED

(MailNews Core :: Networking: NNTP, defect, P3)

Description

[Tomas Ögren]

I mid-mouse clicked on the
news://news.mozilla.org/[e-mail] link on
tinderbox and got these asserts:
WEBSHELL+ = 5
assuming d&d is off for Personal Toolbar
WEBSHELL+ = 6
Setting content window
FOR DEBUG BUILDS ONLY:  we are forcing you to see the checkin guidelines when
you open a browser window
Loading page specified via openDialog
###!!! ASSERTION: couldn't lazily create the server
: 'NS_SUCCEEDED(rv)', file nsMsgAccount.cpp, line 96
###!!! Break: at file nsMsgAccount.cpp, line 96
###!!! ASSERTION: couldn't lazily create the server
: 'NS_SUCCEEDED(rv)', file nsMsgAccount.cpp, line 96
###!!! Break: at file nsMsgAccount.cpp, line 96
###!!! ASSERTION: NS_ENSURE_TRUE(NS_SUCCEEDED(DoURILoad(aURI, aReferrer, loadCmd
, aWindowTarget, aPostData))) failed: '(!((DoURILoad(aURI, aReferrer, loadCmd,
aWindowTarget, aPostData)) & 0x80000000))', file nsDocShell.cpp, line 2288
###!!! Break: at file nsDocShell.cpp, line 2288
###!!! ASSERTION: NS_ENSURE_TRUE(NS_SUCCEEDED(InternalLoad(aURI, referrer, 0, 0,
replace ? loadNormalReplace : loadNormal))) failed: '(!((InternalLoad(aURI,
referrer, 0, 0, replace ? loadNormalReplace : loadNormal)) & 0x80000000))', file
nsDocShell.cpp, line 213
###!!! Break: at file nsDocShell.cpp, line 213
###!!! ASSERTION: NS_ENSURE_TRUE(NS_SUCCEEDED(LoadURI(uri, 0))) failed:
'(!((LoadURI(uri, 0)) & 0x80000000))', file nsDocShell.cpp, line 1054
###!!! Break: at file nsDocShell.cpp, line 1054
JavaScript error:
 line 0: uncaught exception: [Exception... " 0x80004005 (NS_ERROR_FAILURE)
[nsIBrowserInstance.loadUrl]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)" 
location: "JS frame :: chrome://navigator/content/navigator.js ::
onLoadViaOpenDialog :: line 379"  data: no]

in SetSecurityButton
WEBSHELL+ = 7
Document: Done (956882380.188 secs)
Document about:blank loaded successfully

Blank page loaded with beeps in my face.
Closed the app, started up again and just hit File->New->Message and got these
asserts:
WEBSHELL+ = 8
WEBSHELL+ = 9

ComposeLoad from XUL
###!!! ASSERTION: couldn't lazily create the server
: 'NS_SUCCEEDED(rv)', file nsMsgAccount.cpp, line 96
###!!! Break: at file nsMsgAccount.cpp, line 96
###!!! ASSERTION: couldn't lazily create the server
: 'NS_SUCCEEDED(rv)', file nsMsgAccount.cpp, line 96
###!!! Break: at file nsMsgAccount.cpp, line 96
###!!! ASSERTION: couldn't lazily create the server
: 'NS_SUCCEEDED(rv)', file nsMsgAccount.cpp, line 96
###!!! Break: at file nsMsgAccount.cpp, line 96
prefillAccount = null
Compose: ComposeStartup
[format=0]
[type=0]
[nsIMsgIdentity: id2]
JavaScript error:
 line 0: uncaught exception: [Exception... " 0x80004005 (NS_ERROR_FAILURE)
[nsISupportsArray.QueryElementAt]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)" 
location: "JS frame ::
chrome://messenger/content/messengercompose/MsgComposeCommands.js ::
ComposeStartup :: line 181"  data: no]

Comment 1

[(not reading, please use [e-mail] instead)]

accepting.  i understand what's going on here.  I may have a duplicate of the 
news:// problems, but not the new message problem.  (but they are related.)

Comment 2

[(not reading, please use [e-mail] instead)]

moving to m18.

Comment 3

[timeless]

It looks like this was fixed, sspitzer do you want to mark as fixed?
9/15-05 w32 talkback
Entering news://news.mozilla.org/[e-mail] 
worked
File>New>Message gave me the account wizard [I think this bug should be just 
about this]
news://news.mozilla.org:119/netscape.public.mozilla.xpcom did not seem to work 
[i think this is probably in some other bug]

Comment 4

[timeless]

Seth: I think you can mark this bug as fixed. Unless you want to do more 
cleanup.  New message spawns the account wizard [although it seems the logic is 
a bit too reckless] <output>

ComposeLoad from XUL
attempt to UpgradePrefs.  If that fails, open the account wizard.
Compose: ComposeStartup
[format=0]
[type=0]

JavaScript error:
 line 0: uncaught exception: [Exception... "Component returned failure code: 
0x8
0004005 (NS_ERROR_FAILURE) [nsIMsgAccountManager.defaultAccount]"  nsresult: 
"0x
80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: 
chrome://messenger/content/
messengercompose/MsgComposeCommands.js :: ComposeStartup :: line 586"  data: 
no]


************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "msgCompose has no properties" {file: 
"chrome:
//messenger/content/messengercompose/MsgComposeCommands.js" line: 230}] 
[nsICont
roller::isCommandEnabled]"  nsresult: "0x80570021 
(NS_ERROR_XPC_JAVASCRIPT_ERROR
_WITH_DETAILS)"  location: "JS frame :: 
chrome://global/content/globalOverlay.js
 :: goUpdateCommand :: line 57"  data: yes]
************************************************************
An error occurred updating the cmd_showFormatToolbar command
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "msgCompose has no properties" {file: 
"chrome:
//messenger/content/messengercompose/MsgComposeCommands.js" line: 230}] 
[nsICont
roller::isCommandEnabled]"  nsresult: "0x80570021 
(NS_ERROR_XPC_JAVASCRIPT_ERROR
_WITH_DETAILS)"  location: "JS frame :: 
chrome://global/content/globalOverlay.js
 :: goUpdateCommand :: line 57"  data: yes]
************************************************************
An error occurred updating the cmd_showFormatToolbar command
Updating wizard map..
got a request
** acctype onload
Calling custom onInit()

The other urls work [the news group url requires a news server to be 
configured, the news message one does not]

Comment 5

[(not reading, please use [e-mail] instead)]

clearing milestone, m17 and m18 are meaningless now.  these need to be triages
along with the rest.

Comment 7

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 8

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 9

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

jcranmer, -> News, or can this be resolved somehow?

Comment 10

[Joshua Cranmer [:jcranmer]]

While the specific assertions are no longer there, the URIs still fail, although with NS_ENSURE_SUCCESS warnings.

Comment 11

[Joshua Cranmer [:jcranmer]]

This was fixed by one of the patches in bug 226890, note that it has its own test (test_bug34765.js).