SpecialPowers.spawn (and potentially other SpecialPowers APIs?) like to throw "OperationError: The operation failed for an operation-specific reason" which is unhelpful for narrowing down what's actually going wrong
Categories
(Testing :: Mochitest, defect, P2)
Tracking
(Fission Milestone:M4.1, firefox73 fixed)
Tracking | Status | |
---|---|---|
firefox73 | --- | fixed |
People
(Reporter: Gijs, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
Bug 1588839 - Part 2: Return the actual rejection value when a sendQuery handler rejects. r=bzbarsky
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
This is confusing both for local debugging and for the intermittents that are being filed for this error that then obscure what the actual error is. Causes I've seen so far include:
- passing broken arguments (e.g. null as the 'args' parameter)
- errors in the execution of the spawned task (e.g. ReferenceError when referencing functions that don't exist, attempting to access properties on things that are null, etc.)
Comment 1•5 years ago
|
||
Kris, did you have some bug on file for this already?
Comment 2•5 years ago
|
||
I'm marking this as blocking Fission mochitests because it makes fixing them way more annoying.
Assignee | ||
Comment 3•5 years ago
|
||
No, but I've been working on it.
Assignee | ||
Comment 4•5 years ago
|
||
This is necessary for sanity checking values sent from content processes
before using them with APIs which require SavedFrame objects.
Assignee | ||
Comment 5•5 years ago
|
||
In order to be able to reasonably debug error results from things like
JSWindowActor.sendQuery, we need to be able to clone errors across process
boundaries, so that they can be propagated to the caller that initiated a
query. The standard for the structured clone algorithm does not allow cloning
errors directly, so this patch instead adds a chrome-only wrapper object which
supports structured clone writing, and on reading, automatically decodes to
the error object it wraps. Callers who wish to clone an Error or Exception
object simply need to wrap it in a ClonedErrorHolder before sending.
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
This makes it much simpler to track down the source of message handler errors
by linking the cross-process caller chains which sent the problematic message.
Comment 8•5 years ago
|
||
The priority flag is not set for this bug.
:ahal, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
Backed out 4 changesets (bug 1588839) for causing JSWindowActor.cpp failures
push that caused the backout: https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=280136038&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=7cfcd0f5da4f6b01c93697f5d212fe3db679df89
backout: https://hg.mozilla.org/integration/autoland/rev/8a2f3dae304dbf22bf8305dfaaf7db75a8a5aba9
Assignee | ||
Updated•5 years ago
|
Comment 12•5 years ago
|
||
Comment 13•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/df371f905d3a
https://hg.mozilla.org/mozilla-central/rev/e4783542b7c8
https://hg.mozilla.org/mozilla-central/rev/c51a9a372a81
https://hg.mozilla.org/mozilla-central/rev/aa4e0207b45f
Updated•5 years ago
|
Description
•