Closed Bug 1406774 Opened 7 years ago Closed 6 years ago

Debugger broken outside safe mode

Categories

(DevTools :: Debugger, defect)

56 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: inkatadoc, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171003101344

Steps to reproduce:

Try to use the Javascript debugger.

F12 -> choose debugger tab


Actual results:

Debug tab open, but nothing works. Javascript files do not load, cannot set breakpoints. The main panel is blank.

HOWEVER

If I start in safe mode, the debugger works fine.

I tried multiple combinations of safe mode and/or refresh profile and the only consistent way to get a working debugger is in safe mode.




Expected results:

Launching FF in the console, I get the following error

console.error: 
  Message: TypeError: str is null
  Stack:
    KeyShortcuts.parseElectronKey@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:37806:8
on@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:37942:23
componentDidMount@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:24286:6
notifyAll@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:842:9
close@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:14599:5
closeAll@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:19101:11
perform@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:19048:11
batchedMountComponentIntoNode@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:12357:3
perform@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:19035:13
batchedUpdates@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:10660:7
batchedUpdates@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:16668:3
_renderNewRootComponent@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:12551:5
_renderSubtreeIntoContainer@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:12632:21
render@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react.js:12653:12
monkeyPatchRender/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/shared/vendor/react-dom.js:128:14
renderRoot@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:3409:6
bootstrapApp@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:32502:5
onConnect</_ref<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:31465:7
step@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:31491:184
step/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/debugger/new/debugger.js:31491:362

IF I launch FF with the --safe-mode flag, no errors are produced and the debugger works fine.
Component: Untriaged → Developer Tools: Debugger
I couldn't find any bug like this, is this a known issue?

Thanks guys!
ping
Product: Firefox → DevTools
Hello inkatadoc!  Were you on Spanish (MX) language?  If so I believe we've found the fix today.  Please let me know!
Flags: needinfo?(inkatadoc)
I'm not positive, but it's highly probable. I mean I'm sure my interface is in spanish, but not sure if it was the MX variant.
UPDATE!

debugger works in FF63 Linux!!!
Flags: needinfo?(inkatadoc)
Excellent!
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.