"Unexpected invalid url: debugger eager eval code" when typing anything in the console of an extension page
Categories
(DevTools :: Console, defect, P2)
Tracking
(firefox76 fixed)
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: robwu, Assigned: rpl)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
When I type anything in the console of the devtools in a moz-extension:
-page, then I see "Unexpected invalid url: debugger eager eval code" being spammed to the global JS console.
STR:
- Install an extension (e.g. uBlock Origin) if you don't have any extension installed.
- Visit
about:debugging
and use the "Inspect" button of any extension to launch the developer tools for amoz-extension:
-page (the background page in this case, but any other page would have worked). - Type anything, e.g. the letter
b
in the devtools console. - Look at the console. If it is empty, look at the global JS console (Ctrl-Shift-J).
Expected:
- No errors
Actual:
- The following error is repeatedly shown for every keystroke:
Unexpected invalid url: debugger eager eval code webextension.js:351
_allowSource resource://devtools/server/actors/targets/webextension.js:351
<anonymous> self-hosted:875
allowSource resource://devtools/server/actors/utils/TabSources.js:37
_addSource resource://devtools/server/actors/thread.js:1888
onNewScript resource://devtools/server/actors/thread.js:1859
onNewScript self-hosted:875
getEvalResult resource://devtools/server/actors/webconsole/eval-with-debugger.js:204
evalWithDebugger resource://devtools/server/actors/webconsole/eval-with-debugger.js:164
evaluateJS resource://devtools/server/actors/webconsole.js:1182
evaluateJSAsync resource://devtools/server/actors/webconsole.js:1077
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:111
Tested with Firefox Nightly 75.0a1 buildID 20200309091841 and Firefox Nightly 76.0a1 buildID 20200323092419
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Assignee | ||
Comment 2•5 years ago
|
||
As for sources with url "debugger eval code", webExtensionTargetPrototype._allowSource should also filter out
sources with url "debugger eager eval code" without logging any error (as it is an source.url value that we
expect and that we already know that it isn't a valid URI, and we know that those sources shouldn't be listed
in the debugger panel).
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D68183
Comment 5•5 years ago
|
||
Backed out for perma failures on browser_jsterm_eager_evaluation_on_webextension_target.js.
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=295560259&repo=autoland&lineNumber=1074
Backout: https://hg.mozilla.org/integration/autoland/rev/c4100c990ddccddae62224bc575090ee78a405be
Assignee | ||
Comment 6•5 years ago
|
||
The test case was failing because it was pushed on autoland and ended to be applied on top of Bug 1625495's patch which has renamed "devtools/client/shared/devtools-client" to "devtools/client/devtools-client".
I'm actually glad that this didn't happen the other way around (and risk Bug 1625495 to be backed out because of the unexpected failure on the new test case added in second patch attached to this issue).
I've just updated the patch and I'll push it to autoland again asap.
Comment 8•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/21e6f132abfb
https://hg.mozilla.org/mozilla-central/rev/c8fc3d9a00bb
Updated•5 years ago
|
Description
•