1743597 - Debugger panel has crashed

Status: RESOLVED DUPLICATE of bug 1739382

(DevTools :: Debugger, defect)

Description

[mail]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

I develop a web app with React, Typescript, Less and webpack. Source maps are enabled an.. The setup has been the same for over a year.

I wrote a debugger statement in order to debug a function I just wrote. I tried to refresh the browser (I don't remember if I DID press f5) while dev tools are opened (a long running session). I switched from my editor to the browser window and.. dev tools crashed.

Actual results:

The Debugger panel has crashed.
File Bug Report
Error: source source-webpack-internal:///./src/helpers.ts/originalSource-34aba014e8b35c0c5c5bababcc71c585 does not exist
React Component Stack

componentStack

in Connect(SecondaryPanes)

in div

in div

in SplitBox

in div

in A11yIntention

in AppErrorBoundary

in div

in App

in Connect(App)

in Provider

in Provider
Stacktrace

getSourceFromId@resource://devtools/client/debugger/src/reducers/sources.js:533:11

mapStateToProps@resource://devtools/client/debugger/src/components/SecondaryPanes/index.js:491:61

mapToPropsProxy@resource://devtools/client/shared/vendor/react-redux.js:1776:92

handleNewState@resource://devtools/client/shared/vendor/react-redux.js:1937:41

handleSubsequentCalls@resource://devtools/client/shared/vendor/react-redux.js:1954:30

pureFinalPropsSelector@resource://devtools/client/shared/vendor/react-redux.js:1959:32

runComponentSelector@resource://devtools/client/shared/vendor/react-redux.js:1233:39

onStateChange@resource://devtools/client/shared/vendor/react-redux.js:1406:23

notify@resource://devtools/client/shared/vendor/react-redux.js:1159:21

notifyNestedSubs@resource://devtools/client/shared/vendor/react-redux.js:1198:20

onStateChange@resource://devtools/client/shared/vendor/react-redux.js:1409:16

dispatch@resource://devtools/client/shared/vendor/redux.js:265:7

waitUntilService/</<@resource://devtools/client/debugger/src/actions/utils/middleware/wait-service.js:71:24

promiseMiddleware/</<@resource://devtools/client/debugger/src/actions/utils/middleware/promise.js:46:14

context/</<@resource://devtools/client/debugger/src/actions/utils/middleware/context.js:35:12

thunk/</</<@resource://devtools/client/debugger/src/actions/utils/middleware/thunk.js:29:100

dispatch@resource://devtools/client/shared/vendor/redux.js:681:28

mapFrames/<@resource://devtools/client/debugger/src/actions/pause/mapFrames.js:146:13

Close and reopen the toolbox to clear this error.

Expected results:

I should have been able to debug my source code. I've been using your dev tools for years, even when it was called firebug, and I don't ever remember it crashing.

This does not happen for the first time - probably the second in a week or month at most.

It is very unlikely that you will get ANY reports when you require registration. Please make the github registration button more prominent.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Hubert Boma Manilla (:bomsy)]

Thanks for reporting mail,
Would you be able to provide an online sample of the app so we can repro the issue?

Thanks

Comment 3

[mail]

I wish I could isolate the issue. I am a programmer myself and I know how much it sucks when you can't get easily reproducible steps. I always assumed Firefox would collect these by itself on crash - and I believe I've always allowed collection of stack traces/crash dumps.

I was (and still am) concentrating on fixing a difficult bug in my own application, so my attention span is very limited to anything happening outside my own source code right now. If it happens again I will try to find out how to reproduce it reliably.

Comment 4

[Hubert Boma Manilla (:bomsy)]

This looks like the same issue which is getting fixed in Bug 1739382.
I'll close this in favour of that.
Once that lands and the issue still occurs, feel free to reopen.