1249963 - JavaScript error: resource://gre/components/nsMailNewsCommandLineHandler.js, line 41: uncaught exception: 2147942487

Status: RESOLVED WORKSFORME

(MailNews Core :: Backend, defect)

Description

[Martin Mokrejs]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
Build ID: 20160218002054

Steps to reproduce:

Please refer to bug #1219015 . The message is logged by seamonkey-2.38 and 2.39 at least.

Comment 1

[Wayne Mery (:wsmwk)]

(not sure where this should go, but Mailnews Core seems wrong)

Comment 2

[:aceman]

The file actually is in /mailnews so let's keep it there for now. Maybe it is only a problem in SM.

The line 41 is this:
mailURL = aCommandLine.handleFlagWithParam("mail", false);

Martin, do you start TB or SM with a command line argument -mail or something like that?

Comment 3

[Martin Mokrejs]

I have somewhere in settings that mailer comes up by default upon seamonkey is executed, so I assume it is the same as -mailer on a command line.

Comment 4

[:aceman]

I can't reproduce that on TB with the command line argument and TB does not have that setting which window should come up at start up (it only has a single window). Maybe this can only be seen on Seamonkey.

Comment 5

[Philip Chee]

It's inside a try catch block so I don't know why it's an uncaught error.

2147942487 == NS_ERROR_ILLEGAL_VALUE

Comment 6

[Kent James (:rkent)]

(In reply to Philip Chee from comment #5)
> It's inside a try catch block so I don't know why it's an uncaught error.
> 
> 2147942487 == NS_ERROR_ILLEGAL_VALUE

XPCOM components if they throw an error will get logged, even if protected by try/catch. There's a bug somewhere complaining about this, marked WONTFIX.

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to Kent James (:rkent) from comment #6)

(In reply to Philip Chee from comment #5)

It's inside a try catch block so I don't know why it's an uncaught error.

2147942487 == NS_ERROR_ILLEGAL_VALUE

XPCOM components if they throw an error will get logged, even if protected
by try/catch. There's a bug somewhere complaining about this, marked WONTFIX.

I didn't read all of these, but none seem an obvious match

Comment 8

[Magnus Melin [:mkmelin]]

We can close this. The relevant code has changed too much to say anything about whether it even exists in some form anymore.