1160818 - When reporting a cert error (from certerror page), browser console says "Sending message that cannot be cloned. Are you trying to send an XPCOM object?"

Status: RESOLVED FIXED

(Firefox :: Security, defect)

Description

[Daniel Holbert [:dholbert]]

STR:
 1. Visit a page that triggers a cert error.
    (Currently https://saml.yammer.com/ is broken (bug 1160817) & is hence a good test page. There may be others.)

 2. Click "Report this error", and then the "Report" button.

 3. Check your Browser Console.

ACTUAL RESULTS:
This appears in browser console:
> Sending message that cannot be cloned. Are you trying to send an XPCOM object?
>  content.js:276:0

The content.js text is linking to this line of code:
> sendAsyncMessage("Browser:SendSSLErrorReport", {
https://mxr.mozilla.org/mozilla-central/source/browser/base/content/content.js#276

Comment 1

[Daniel Holbert [:dholbert]]

This happens regardless of whether e10s is enabled, FWIW.

Setting dependency on bug 846489 (where mgoodwin added the sendAsyncMessage("Browser:SendSSLErrorReport" call in question), and on bug 1139718 where billm added the "cannot be cloned" error message. (much more recently)

billm, does this error indicate that the sendAsyncMessage() call needs fixing? Can you suggest what someone (mgoodwin perhaps) would need to do to fix it?

Comment 2

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Attachment: patch

This should take care of it.

Comment 3

[Mark Goodwin [:mgoodwin]]

I (also) noticed this issue when working on bug 1088141 and fixed it there.