Browser console crashes every time I click "Show/hide message details" next to network request log line
Categories
(DevTools :: Console, defect, P2)
Tracking
(firefox-esr128 unaffected, firefox136 unaffected, firefox137 fixed, firefox138 fixed)
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox136 | --- | unaffected |
firefox137 | --- | fixed |
firefox138 | --- | fixed |
People
(Reporter: gwarser, Assigned: jdescottes)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:138.0) Gecko/20100101 Firefox/138.0
Steps to reproduce:
-ctrl+shift+j
-enable multiprocess
-enable xhr and requests logging
-enable all settings under the cog wheel in top right
-re/load some page
-click the triangle before networks request line
Actual results:
The Console panel has crashed.
File Bug Report
TypeError: serviceContainer.getToolboxStore is not a function
React Component Stack
in MessageContainer
in LazyMessageList
in div
in ConsoleOutput
in Connect(ConsoleOutput)
in div
in div
in App
in Connect(App)
in AppErrorBoundary
in LocalizationProvider
in Provider
in Provider
Stacktrace
NetworkEventMessage@resource://devtools/client/webconsole/components/Output/message-types/NetworkEventMessage.js:205:35
render@resource://devtools/client/webconsole/components/Output/MessageContainer.js:79:12
finishClassComponent@resource://devtools/client/shared/vendor/react-dom.mjs:10634:31
updateClassComponent@resource://devtools/client/shared/vendor/react-dom.mjs:10597:44
beginWork@resource://devtools/client/shared/vendor/react-dom.mjs:11415:16
performUnitOfWork@resource://devtools/client/shared/vendor/react-dom.mjs:14698:12
workLoop@resource://devtools/client/shared/vendor/react-dom.mjs:14716:24
renderRoot@resource://devtools/client/shared/vendor/react-dom.mjs:14799:15
performWorkOnRoot@resource://devtools/client/shared/vendor/react-dom.mjs:15651:17
performWork@resource://devtools/client/shared/vendor/react-dom.mjs:15563:24
performSyncWork@resource://devtools/client/shared/vendor/react-dom.mjs:15537:14
interactiveUpdates$1@resource://devtools/client/shared/vendor/react-dom.mjs:15804:7
interactiveUpdates@resource://devtools/client/shared/vendor/react-dom.mjs:1897:10
dispatchInteractiveEvent@resource://devtools/client/shared/vendor/react-dom.mjs:4324:21
Close and reopen the toolbox to clear this error.
Expected results:
See request details
Comment 3•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Console' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Assignee | ||
Comment 4•5 months ago
|
||
Oh right that must be from Bug 1849920.
I am not adding the method to the serviceContainer when there is no toolbox, which is the case for the browser console.
Comment 5•5 months ago
|
||
Set release status flags based on info from the regressing bug 1849920
Assignee | ||
Comment 6•5 months ago
|
||
The toolbox store is not available in the Browser Console.
The netmonitor's TabboxPanel component now exports two variants:
- TabboxPanel: raw TabboxPanel without toolbox store derived props
- ConnectedTabboxPanel: connected to the toolbox store for override props
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Assignee | ||
Comment 8•5 months ago
|
||
The toolbox store is not available in the Browser Console.
The netmonitor's TabboxPanel component now exports two variants:
- TabboxPanel: raw TabboxPanel without toolbox store derived props
- ConnectedTabboxPanel: connected to the toolbox store for override props
Original Revision: https://phabricator.services.mozilla.com/D241159
Updated•5 months ago
|
Comment 9•5 months ago
|
||
beta Uplift Approval Request
- User impact if declined: Browser Console shows error screen when clicking on a network request
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: -
- Risk associated with taking this patch: Low
- Explanation of risk level: Simple JS fix, covered with automated tests, devtools only
- String changes made/needed: -
- Is Android affected?: no
Updated•5 months ago
|
Reporter | ||
Comment 10•5 months ago
|
||
Can you tell me, the "File Bug Report" button is doing something for you? Does nothing for me. Will it be fixed here?
Comment 11•5 months ago
|
||
bugherder |
Comment 12•5 months ago
|
||
(In reply to gwarser from comment #10)
Can you tell me, the "File Bug Report" button is doing something for you? Does nothing for me. Will it be fixed here?
It's going to be fixed as part of Bug 1953384 (a patch was pushed already, should be in tomorrow's Nightly)
Updated•5 months ago
|
Comment 13•5 months ago
|
||
uplift |
Description
•