"ReportSiteIssueHelper:GetLog: message reply cannot be cloned." from Report site issue
Categories
(Web Compatibility :: Tooling & Investigations, defect, P2)
Tracking
(firefox103 fixed)
Tracking | Status | |
---|---|---|
firefox103 | --- | fixed |
People
(Reporter: saschanaz, Assigned: twisniewski)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Expected: A new tab should open
Actual: Nothing happens. Multiprocess Browser Toolbox says:
[Exception... "ReportSiteIssueHelper:GetLog: message reply cannot be cloned." nsresult: "0x80004005 (DataCloneError)" location: "<unknown>" data: no] ExtensionCommon.jsm:724
normalizeError resource://gre/modules/ExtensionCommon.jsm:724
recvAPICall resource://gre/modules/ExtensionParent.jsm:1062
(Async: promise callback)
recvAPICall resource://gre/modules/ExtensionParent.jsm:1053
AsyncFunctionNext self-hosted:715
(Async: async)
recvAPICall self-hosted:1198
_recv resource://gre/modules/ConduitsChild.jsm:82
receiveMessage resource://gre/modules/ConduitsParent.jsm:450
WebCompat Reporter: unexpected error Error: An unexpected error occurred background.js:26:15
<anonymous> moz-extension://a5abb3d7-0bfe-42fb-ad72-cfd7d7f66624/background.js:26
(Async: promise callback)
<anonymous> moz-extension://a5abb3d7-0bfe-42fb-ad72-cfd7d7f66624/background.js:21
This does not happen when I try the same on Bugzilla.
Comment 1•3 years ago
|
||
Seems like it's only specific sites, and not general reporter breakage, which is good.
Tom, do you have time to look into that soon'ish? If not, let me know and I'll dig into that. :)
Assignee | ||
Comment 2•3 years ago
•
|
||
Ah, the problem turns out to be that they're logging JS Symbol objects to the console, which don't structured clone. This is easy enough to fix, we just need to add this to the cases in getPreview
, here:
case "symbol":
return value.toString();
I'll post a patch for review soon.
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Backed out for causing for causing mochitest failures on browser_report_site_issue.js
Backout link
Push with failures
Link to failure log
Failure line :
TEST-UNEXPECTED-FAIL | browser/extensions/report-site-issue/test/browser/browser_report_site_issue.js | Test timed out
Assignee | ||
Comment 6•3 years ago
|
||
Well, that's nonsensical. I wonder if it's related to Fission, since I see something similar here: https://bugzilla.mozilla.org/show_bug.cgi?id=1248632
I'd rather have some test coverage than none, so I'll try re-landing with the tests disabled in Fission later, to confirm if that's the likely culprit.
Assignee | ||
Comment 7•3 years ago
|
||
No, I was wrong. It looks like the failed job in that try-run was running in e10s, not without it. so I'm... at a complete loss. For now I'll disable that test so we can at least fix the feature, and we can file a follow-up to determine what might be going on here.
Updated•3 years ago
|
Description
•