Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unverified breakpoints after 2.12.1 release #378

Open
AnrDaemon opened this issue Jan 10, 2025 · 6 comments
Open

Unverified breakpoints after 2.12.1 release #378

AnrDaemon opened this issue Jan 10, 2025 · 6 comments
Labels
needs more info Blocked by feedback from the reporter

Comments

@AnrDaemon
Copy link

Type: Bug

launch.json configuration:

{
            "log": {
                "fileLevel": {
                    "default": "Debug"
                },
                "fileName": "${workspaceFolder}/logs/ffdebug.log"
            },
            "name": "FFdebug",
            "pathMappings": [
                {
                    "path": "${workspaceFolder}/app/",
                    "url": "http://127.0.0.1:5500"
                },
                {
                    "path": "${workspaceFolder}/app/",
                    "url": "https://proto.example.com/"
                },
                {
                    "path": "${workspaceFolder}/app/",
                    "url": "https://stage.example.com/"
                }
            ],
            "preLaunchTask": "Firefox debugger",
            "request": "attach",
            "skipFiles": [
                "**/js.stripe.com/**/*",
                "**/static.sumsub.com/**/*",
                "**/node_modules/**/*",
                "**/*.min.js",
                "${workspaceFolder}/app/lib/tools.js"
            ],
            "host": "127.0.0.1",
            "type": "firefox"
        }

After upgrading to 2.12.1 release and restarting the debugger, I'm unable to verify any of the breakpoints. I have tried to restart both the IDE and the browser to get it to work, but then it would catch a breakpoint in the newly opened tab and don't show it in the IDE.
I have to close all tabs in the browser but one and restart the debugger to connect it again.

Extension version: 2.12.1
VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info
Item Value
CPUs Intel(R) Core(TM) i3-8145U CPU @ 2.10GHz (4 x 2304)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 7.86GB (0.24GB free)
Process Argv --folder-uri file:///d%3A/Profiles/anrdaemon/Documents/hk/invapi-php
Screen Reader no
VM 0%
@hbenl
Copy link
Collaborator

hbenl commented Jan 10, 2025

This could be caused by a bug that I just fixed in version 2.13.0. Could you retry with that version?

@AnrDaemon
Copy link
Author

AnrDaemon commented Jan 10, 2025

Tested, not fixed. To shed a little more light (I don't think that's relevant, but just in case):
The application uses custom click handlers over internal protocol prefixes (like <a href="smth:ID"> … </a> will open the entity smth with specified ID, the ctrl/middle click will window.open() a specific URL with GET params (like, http://example.com/?entity=smth&id=ID). There's the problem starts.
The log shows that breakpoints are recognized, the browser will correctly stop at the breakpoints, but IDE will not show the interface, and it still shows the ghost tabs in threads list.

Restarting the debugger in the IDE may help to revive the system. Or not. Or in the last try it outright forgot that we're debugging and breakpoints ceased to work.

Had to reduce tabs to one and reload debugger again to make it behave.

@hbenl
Copy link
Collaborator

hbenl commented Jan 10, 2025

Which version of Firefox do you use? I've noticed a bug in the current Developer and Nightly editions that could cause this. If you've used one of those, try with the stable edition and tell me if that works better.

@AnrDaemon
Copy link
Author

I'm using current stable releases.
Right now it's 134.0 (64-bit)

@hbenl
Copy link
Collaborator

hbenl commented Jan 13, 2025

OK, so this is a different issue. Could you share your logs/ffdebug.log?

@hbenl hbenl added the needs more info Blocked by feedback from the reporter label Jan 14, 2025
@AnrDaemon
Copy link
Author

I'll have to try and reproduce it with a safe data. Will take a day or two. Sorry for delays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info Blocked by feedback from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants