431622 - NS_NOINTERFACE errors (Fallout from bug 413781)

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Joe Sabash [:JoeS1]]

Now that the console spam has diminished since bug 428600 fix,
I see the following console messages:

New message in inbox:
Error: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]
Source file: chrome://messenger/content/mail-folder-bindings.xml
Line: 132


Delete message in inbox:
Error: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]
Source file: chrome://messenger/content/mail-folder-bindings.xml
Line: 143


Send message: (assume item added to sent folder)
Error: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]
Source file: chrome://messenger/content/mail-folder-bindings.xml
Line: 132

These errors don't seem to effect functionaity in any way, but should
be addressed in the interest of a clean console for TB 3.0a1 release.

Comment 2

[Mark Banner (:standard8)]

Joe, I don't see this on version 3.0a1pre (2008050210), have you got some steps to reproduce?

Comment 3

[Joe Sabash [:JoeS1]]

(In reply to comment #2)
> Joe, I don't see this on version 3.0a1pre (2008050210), have you got some steps
> to reproduce?
> 
Nothing special, anytime a folder is changed (item added, or deleted) 
Started right after the che checkin for bug 413781
Still there in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050503 Thunderbird/3.0a1pre ID:2008050503

Note that bug 432536 noted them as well.
Haven't tried safe mode, but here's my extension list:
Console² 0.3.9
DOM Inspector 2.0.0
EditHtml 0.1.2
Lightning 0.6a1
Nightly Tester Tools 1.3
Provider for Google Calendar 0.4 [DISABLED]

Comment 4

[Mark Banner (:standard8)]

I forgot to mention, I'm on Mac, so this could be Windows specific.

Comment 5

[Phil Ringnalda (:philor)]

It's not Windows specific; I think it's "have a profile with one of the forms of broken half-server that Joey exposed." I'd bet that clean profile, click the link in bug 41133 comment 8 (and maybe restart, if that part's true), then delete mail would do it.

Comment 6

[Magnus Melin [:mkmelin]]

Yes i get this on linux (safe-mode too). I have only my first account set to check new mail automatically. I get the error if I click the "get mail" button, select an account from that dropdown list, and actually get some new mail.

Comment 7

[Joe Sabash [:JoeS1]]

Further info:
This looks like a profile related problem, I'm no longer seeing the errors.
Prior to yesterday, I have been using a zip build and using software update to download partials, or full downloads as required. After installing an installer build on the same profile, the errors went away, even when I returned to the zip build. So something in the installer sequence did something to fix things.

I'll try to compare the saved profile with the resulting profile(after the installer) to see if I can pin it down.

This could explain why Magnus (linux) and Marsha (Mac) are both seeing the errors, since there is no intsaller with those builds.

Unrelated to this bug, use of the installer did change a few security prefs that I had set back to default values after the intall (that should not happen)

Comment 8

[Mark Banner (:standard8)]

(In reply to comment #2)
> Joe, I don't see this on version 3.0a1pre (2008050210), have you got some steps
> to reproduce?
> 
So I'm now seeing this on my debug builds.

Comment 9

[Joe Sabash [:JoeS1]]

The errors are back again for me.
The intaller build over my trunk profile chased them away, and partial software updates seemed to work OK.
The last thing I did was to install a full hourly zip over my existing build, and now they are back. Hope this gives someone a clue.

Comment 10

[Dan Mosedale (:dmosedale, :dmose)]

Marking as blocking Thunderbird 3 since this is a regression.

Comment 11

[Joey Minta]

I'm pretty sure this was fixed by one of the other patches to the binding.

Comment 12

[Joe Sabash [:JoeS1]]

I haven't seen these errors lately.
Will watch closely for the next few days, then WORKSFORME

Comment 13

[Joe Sabash [:JoeS1]]

After 8-10 hours of runtime, none of the errors have occurred.
Marking worksforme for lack of a specific bug fix.