Empty Error Dialog Displayed When Trying to Launch

[mp035]

Hi, I have installed the extension and configured launch.json as specified in the documents, but upon trying to launch the debugger, all I get is an empty error dialog. See image:

I am running the following build of VsCode:

Version: 1.90.0
Commit: 89de5a8d4d6205e5b11647eb6a74844ca23d2573
Date: 2024-06-04T19:43:07.605Z
Electron: 29.4.0
ElectronBuildId: 9593362
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.6.32-1-MANJARO snap

Is there any way to provide more info (or to view the actual error occurring)?

[DiamondIceNS]

I have also just today started to see this error.

Version: 1.94.2 (system setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045

[DiamondIceNS]

Log is completely empty, too. Whatever's going on, it's crashing before the logger can even write anything.

[DiamondIceNS]

I uninstalled VS Code, re-installed it, disabled all extensions other than this one, and am still getting the issue.

I cloned the repository and tried to debug the extension. Breakpoints and console logs are triggering for initializing the server, but I'm putting breakpoints all over the FirefoxDebugAdapter class and none of them are being hit.

It seems that the ExtensionHost is crashing instantly any time it tries to start. I can see it pop up for a split second in the process explorer whenever I try to attach the debugger. Issue seems to be emitting from inside VS Code itself, or the debug adapter extension that this extension depends on. I don't know if this makes it their problem or if this extension is somehow configuring itself incorrectly.

Curiously, when I change the name of the log file path, it does create a new log file at that path every time I try. Yet, when I place a breakpoint in the Log class responsible for taking the path specified in the configuration and opening a file at that path for writing, it doesn't get hit. Strange. Not really sure what to make of that.

[DiamondIceNS]

Okay, well, now I feel embarrassed.

The problem was happening when Firefox didn't have remote debugging enabled. Enabling that caused it to work as expected.

I could've sworn there used to be an error message for when it couldn't connect that actually gave useful information. If it did, it doesn't seem to anymore. Perhaps a thing to address, should anyone capable feel inclined.