Closed
Bug 1313987
Opened 9 years ago
Closed 9 years ago
promiseWarn() rejects incorrectly
Categories
(DevTools :: Inspector, defect)
DevTools
Inspector
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: marcosc, Assigned: marcosc)
Details
Attachments
(1 file)
|
691 bytes,
patch
|
Details | Diff | Splinter Review |
Seeing:
Protocol error (unknownError): can't access dead object utils.js:157
And it looks like there is a typo there:
return promise.reject(error)
Should be:
return Promise.reject(error);
| Assignee | ||
Comment 1•9 years ago
|
||
Seeing in the browser toolbox, that is.
| Assignee | ||
Comment 2•9 years ago
|
||
Not sure who to assign this to...
Assignee: nobody → mcaceres
Status: NEW → UNCONFIRMED
Ever confirmed: false
| Assignee | ||
Comment 3•9 years ago
|
||
The relevant file is devtools/client/inspector/shared/utils.js:157
| Assignee | ||
Comment 4•9 years ago
|
||
I'm probably wrong about this one... might just be a closure and an ol' school promise and the error is unrelated.
Updated•9 years ago
|
Product: Developer Documentation → Firefox
We do use `promise` with lowercase "p" in much of the DevTools today, which corresponds to the Promise.jsm toolkit library, as a way to avoid clashing with the native JS promises available as `Promise`.
So, `promiseWarn` itself is probably okay. It's likely something earlier up the call stack hit a "can't access dead object" error. :marcosc, what steps are needed to reproduce this?
Component: Developer Tools → Developer Tools: Inspector
Flags: needinfo?(mcaceres)
| Assignee | ||
Comment 6•9 years ago
|
||
I saw it coming up in Developer Edition when I filed the bug, but after some attempts I've not been able to reproduce. I'll keep my eye out for it tho and reopen if it happens again.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(mcaceres)
Resolution: --- → INVALID
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•