Closed Bug 1558423 Opened 6 years ago Closed 6 years ago

TypeError: categories is undefined

Categories

(DevTools :: Debugger, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Honza, Unassigned)

Details

I am seeing the following error in the Browser Console (it makes the entire Debugger panel blank)

Looking at the state:

state.eventListenerBreakpoints.categories is undefined

Could fetching of AVAILABLE_BREAKPOINTS from the backend fail?

Sorry, I don't have STRs, but I still think it's good to file the bug here. It worked before and suddenly stopped.
Of course, creating a new profile helps.

TypeError: categories is undefined

render resource://devtools/client/debugger/src/components/SecondaryPanes/EventListeners.js:148
    finishClassComponent resource://devtools/client/shared/vendor/react-dom-dev.js:13771
    updateClassComponent resource://devtools/client/shared/vendor/react-dom-dev.js:13733
    beginWork resource://devtools/client/shared/vendor/react-dom-dev.js:14402
    performUnitOfWork resource://devtools/client/shared/vendor/react-dom-dev.js:16441
    workLoop resource://devtools/client/shared/vendor/react-dom-dev.js:16480
    renderRoot resource://devtools/client/shared/vendor/react-dom-dev.js:16520
    performWorkOnRoot resource://devtools/client/shared/vendor/react-dom-dev.js:17138
    performWork resource://devtools/client/shared/vendor/react-dom-dev.js:17060
    performSyncWork resource://devtools/client/shared/vendor/react-dom-dev.js:17032
    requestWork resource://devtools/client/shared/vendor/react-dom-dev.js:16932
    scheduleWork$1 resource://devtools/client/shared/vendor/react-dom-dev.js:16796
    scheduleRootUpdate resource://devtools/client/shared/vendor/react-dom-dev.js:17363
    updateContainerAtExpirationTime resource://devtools/client/shared/vendor/react-dom-dev.js:17390
    updateContainer resource://devtools/client/shared/vendor/react-dom-dev.js:17417
    render resource://devtools/client/shared/vendor/react-dom-dev.js:17700
    legacyRenderSubtreeIntoContainer resource://devtools/client/shared/vendor/react-dom-dev.js:17840
    unbatchedUpdates resource://devtools/client/shared/vendor/react-dom-dev.js:17257
    legacyRenderSubtreeIntoContainer resource://devtools/client/shared/vendor/react-dom-dev.js:17836
    render resource://devtools/client/shared/vendor/react-dom-dev.js:17895
    renderPanel resource://devtools/client/debugger/src/utils/bootstrap.js:74
    bootstrapApp resource://devtools/client/debugger/src/utils/bootstrap.js:124
    onConnect resource://devtools/client/debugger/src/client/index.js:98
    bootstrap resource://devtools/client/debugger/src/main.js:31
    open resource://devtools/client/debugger/panel.js:32
    onLoad resource://devtools/client/framework/toolbox.js:2084
Promise-backend.js:926:35
    process resource://gre/modules/Promise-backend.js:926
    walkerLoop resource://gre/modules/Promise-backend.js:807
    scheduleWalkerLoop resource://gre/modules/Promise-backend.js:740
    schedulePromise resource://gre/modules/Promise-backend.js:771
    completePromise resource://gre/modules/Promise-backend.js:708

How/where can I simple check that fetching AVAILABLE_BREAKPOINTS works?
Honza

Flags: needinfo?(dwalsh)

Now happened again in the new profile (Win10)
Honza

Priority: -- → P1

Ah, I was accidentally using different backend (not Logan's build)

Closing

Honza

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Flags: needinfo?(dwalsh)
You need to log in before you can comment on or make changes to this bug.