928240 - Call to xpconnect wrapped JSObject produced this error: * [Exception... "'<error>' when calling method: [nsIContentHandler::handleContent]" nsresult: "0x805d0001 (<unknown>)" location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0" da

Status: NEW

(Toolkit :: Downloads API, defect)

Description

[ISHIKAWA, Chiaki]

This is with comm-central thunderbird.
(I refreshed my source this week. The bug could have been there all along, but I was not paying attention to this bug.)

When I click on a message attachment to bring up a dialog to either save/open the attachment, an error is thrown all the way to the top-level without getting caught.

The following is is the message I see on the terminal window from which TB was invoked from the command shell.
[...]
-DOMWINDOW == 28 (0xb67adc8) [serial = 29] [outer = (nil)] [url = about:blank]
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "'<error>' when calling method: [nsIContentHandler::handleContent]"  nsresult: "0x805d0001 (<unknown>)"  location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0"  data: no]
************************************************************
++DOCSHELL 0xac60790 == 15 [id = 17]
++DOMWINDOW == 29 (0xb4d0640) [serial = 40] [outer = (nil)]
[...]

The following is the copy from the entry in the built-in Error Console of TB:
Timestamp: 2013年10月18日 13時48分43秒
Error: [Exception... "'<error>' when calling method: [nsIContentHandler::handleContent]"  nsresult: "0x805d0001 (<unknown>)"  location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0"  data: no]

An error should be caught before hitting the top-level like this for an interactive program like TB IMHO.

TIA

Comment 1

[ISHIKAWA, Chiaki]

Strange.

This happens only when
 - left clicking on the attachemt name to star the dialog to save an attachment

 - Select the attachment and use context menu right-click and "save as" does not produce his.
 - Use the oernanent [save] button at the lower corner of the message pane [ in the same row 
   where the attachement is shown.] does not produce this.

Also, the message is no longer the same. Now it is shown as,

************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "Async version must be used"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: file:///REF-OBJ-DIR/objdir-tb3/mozilla/dist/bin/components/nsHelperAppDlg.js :: nsUnknownContentTypeDialog.prototype.promptForSaveToFile :: line 207"  data: no]
************************************************************

Even with the message shown, the saving succeeds eventually.
I am not sure what goes on.
(Maybe the caller of functions in 
mozilla/toolkit/mozapps/downloads/nsHelperAppDlg.js

first calls the sync version 
  promptForSaveToFile: function(aLauncher, aContext, aDefaultFile, aSuggestedFileExtension, aForcePrompt) {
    throw new Components.Exception("Async version must be used",    
    Components.results.NS_ERROR_NOT_AVAILABLE);
  },

first, and  then then async version

  promptForSaveToFileAsync: function(aLauncher, aContext, aDefaultFile, aSuggestedFileExtension, aForcePrompt)

 in succession???